Add pragmas to funC for precise control of computation order #589
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#pragma allow-post-modification;- allows expressions likevar t = (ds, ds~load_uint(32));and ensures that in such expression all terms are treated left to right. Without pragma such expressions are forbidden.#pragma compute-asm-ltr;- forces that asm arguments are computed left to right as appear in funC code. Without pragma first reordering in according to asm rules happens and only then arguments are computed.Also inline functions with empty body now allowed: such inlines have no effect on the bytecode.
This changes introduce funC version
0.4.1