Skip to content
New issue

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

🛠️ Minimum Solidity Version will still be ^0.8.4 #527

Open
Vectorized opened this issue Aug 5, 2023 · 2 comments
Open

🛠️ Minimum Solidity Version will still be ^0.8.4 #527

Vectorized opened this issue Aug 5, 2023 · 2 comments

Comments

@Vectorized
Copy link
Owner

Vectorized commented Aug 5, 2023

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:

  • Must be performance related. Better if the performance impact is large.
  • Must require breaking code changes in Solady.

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.

@NoahMarconi
Copy link

any plans to support Cancun? LibString.slice for example should see some minor saving using mcopy over the body of the for loop

@Vectorized
Copy link
Owner Author

@NoahMarconi Ah, we’ll just go for the bleeding edge in Soledge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants