…red accept/reject logic to one mentioned in github discussion thread and compatibility section mentioning 1155+721 hybrid, plus we are now at Solidity 0.5.8 and my email should match github.

# Conflicts:
#	EIPS/eip-1155.md

…given in discussion thread. This introduces specific scenarios and rules to match.

# Conflicts:
#	EIPS/eip-1155.md

…ection and numbered the scenarios to be easily identifiable.

…in text and make sure 1155 json schema title matches the standard section.

# Conflicts:
#	EIPS/eip-1155.md

…inal and subsequently they do our text is not out of date. Users can see the current status of those other standards on the landing page for them.

…there.

Pull James' edits in, some wording changes and clarifications.

…ration, add in "isERC1155TokenReceiver" function and rules around hybrid standard implementations around it. Also made use of `` on types consistent.

# Conflicts:
#	EIPS/eip-1155.md

…eturn text in case anyone is silly enough to copy-paste that and end up always returning true.

# Conflicts:
#	EIPS/eip-1155.md

…nReceiver interface.

# Conflicts:
#	EIPS/eip-1155.md

…ment.

…ce to view instead of pure (to cover fallback versions) but leave recommended impl as pure, be clearer about having to pass the _data arg to the hooks unaltered, make it so all events have to be emitted before any hooks are called so order is preserved.

…" for example.

…e view mutability to match the interface as implementers will have to also if they include it. Rather surprisingly according to remix the "view" version costs 282 gas vs 305 for the "pure" version too.

# Conflicts:
#	EIPS/eip-1155.md

# Conflicts:
#	EIPS/eip-1155.md

# Conflicts:
#	EIPS/eip-1155.md

… send to contracts that don't have receiver functions if the implementation wishes (with warning on potentially unrecoverable tokens).

# Conflicts:
#	EIPS/eip-1155.md

Revert magic_values to original byte4

# Conflicts:
#	EIPS/eip-1155.md