A quick stab at what mapping key information might look like in the format. Intended to be open to future expansion. Figured for different mapping hash formats, it makes more sense to just have an enumeration (that can be expanded in the future) rather than trying to specify them in some sort of DSL. :P There's not just one out there, Solidity and Vyper do things a bit differently here!
(Not sure if "prefix" and "postfix" are intuitive enough, arguably those should be swapped, or they could just be renamed to something less ambiguous.)
I'm assuming this is only used on SHA3 instructions. Potentially one might want to allow some way to mark other sorts of hashes were those ever used for this purpose, but, I figure, there's no need to go addressing that unless someone actually does it, which seems unlikely.
A quick stab at what mapping key information might look like in the format. Intended to be open to future expansion. Figured for different mapping hash formats, it makes more sense to just have an enumeration (that can be expanded in the future) rather than trying to specify them in some sort of DSL. :P There's not just one out there, Solidity and Vyper do things a bit differently here!
(Not sure if "prefix" and "postfix" are intuitive enough, arguably those should be swapped, or they could just be renamed to something less ambiguous.)
I'm assuming this is only used on SHA3 instructions. Potentially one might want to allow some way to mark other sorts of hashes were those ever used for this purpose, but, I figure, there's no need to go addressing that unless someone actually does it, which seems unlikely.
Closes #35.