Skip to content

Issues: ethereum/solidity

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt click/return to exclude labels
or click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

The unary " " in "((x) /= (2 % x)) (-y)" reports an error bug 🐛 low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact selected for development It's on our short-term development
#15236 opened Jul 1, 2024 by haoyang9804
Consider changing linker on Linux from ld.gold to ld build system 🏗️ low effort There is not much implementation work to be done. The task is very easy or tiny. low impact Changes are not very noticeable or potential benefits are limited. nice to have We don’t see a good reason not to have it but won’t go out of our way to implement it.
#15199 opened Jun 14, 2024 by cameel
Update Z3 to 4.13.0 or later build system 🏗️ low effort There is not much implementation work to be done. The task is very easy or tiny. low impact Changes are not very noticeable or potential benefits are limited. must have Something we consider an essential part of Solidity 1.0. smt
#15198 opened Jun 14, 2024 by cameel
ICE in Z3Interface::fromZ3Expr() when running tests on Arch Linux bug 🐛 high impact Changes are very prominent and affect users or the project in a major way. low effort There is not much implementation work to be done. The task is very easy or tiny. must have Something we consider an essential part of Solidity 1.0. smt
#15196 opened Jun 12, 2024 by MariusVanDerWijden
Reuse optimized IR/bytecode for bytecode dependencies high impact Changes are very prominent and affect users or the project in a major way. medium effort Default level of effort must have Something we consider an essential part of Solidity 1.0. optimizer performance 🐎
#15179 opened Jun 4, 2024 by cameel
Deduplicate bytecode dependencies used by both creation and deployed object low effort There is not much implementation work to be done. The task is very easy or tiny. low impact Changes are not very noticeable or potential benefits are limited. performance 🐎 should have We like the idea but it’s not important enough to be a part of the roadmap.
#15178 opened Jun 4, 2024 by cameel
Function selectors from inherited interfaces are not visible in parent interface bug 🐛 low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact should compile without error Error is reported even though it shouldn't. Source is fine.
#15157 opened May 28, 2024 by mnusurov
ProTip! Mix and match filters to narrow down what you’re looking for.