Order of top-level entries in contract should be preserved
Clarification and motivation
It so happens, that changing order of parameter
/contract
/code
entries influences their serialized representation accordingly, would be nice to follow this somehow.
Acceptance criteria
-
PACK
/UNPACK
serialize contracts according to the given top-level entries order. - Pretty printer display contracts according to the given top-level entries order.
Note: this issue was originally reported here. So please make sure there are no TM-96 TODO items in code comments.
Checklist
-
This issue description complies with the guidelines written here. -
I have set the appropriate Type and State and specified the integration branch unless it's master.