We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Target EVM will still be Paris.
For maximum backwards compatibility.
At least until Solidty offers an irresistible feature that allows library authors to write performant, concise code (e.g. macros).
Basically two criteria:
Basically, if you can activate the performance related feature without any changes to Solady, it will not be considered.
Syntactic sugar features, cli-configurable features, better compiler efficiency out-of-the-box features will not be considered.
TSTORE may be in a separate directory excluded from compilation, e.g. exp.
exp
The text was updated successfully, but these errors were encountered:
any plans to support Cancun? LibString.slice for example should see some minor saving using mcopy over the body of the for loop
LibString.slice
mcopy
Sorry, something went wrong.
@NoahMarconi Ah, we’ll just go for the bleeding edge in Soledge.
No branches or pull requests
Target EVM will still be Paris.
For maximum backwards compatibility.
At least until Solidty offers an irresistible feature that allows library authors to write performant, concise code (e.g. macros).
Basically two criteria:
Basically, if you can activate the performance related feature without any changes to Solady, it will not be considered.
Syntactic sugar features, cli-configurable features, better compiler efficiency out-of-the-box features will not be considered.
TSTORE may be in a separate directory excluded from compilation, e.g.
exp
.The text was updated successfully, but these errors were encountered: