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
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort

Issues list

Build error bug πŸ›
#15132 opened May 22, 2024 by Spixmaster
Add EVM Version Prague 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. selected for development It's on our short-term development
#15111 opened May 15, 2024 by ekpyron 0.8.27
SMTChecker is unable to accurately determine the output of bytes.concat needs investigation 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. smt
#15073 opened May 2, 2024 by Subway2023
Bytecode compare runs with two-stage compilation medium effort Default level of effort medium impact Default level of impact must have Something we consider an essential part of Solidity 1.0. testing πŸ”¨
#15063 opened Apr 26, 2024 by cameel 0.8.27
--optimize should not trigger compilation if no optimized output is requested 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.
#15062 opened Apr 26, 2024 by cameel 0.8.27
IR-based Codegen fails to compile at version of 0.8.13 bug πŸ› documentation πŸ“– 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.
#15045 opened Apr 21, 2024 by Subway2023
Avoid tab-space mix in compiler output 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.
#15033 opened Apr 16, 2024 by cameel
ProTip! Adding no:label will show everything without a label.