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

Some EOF-specific Yul builtin names are reserved even outside of EOF 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.
#15672 opened Dec 20, 2024 by cameel 0.8.29
Running syntax tests via IR low impact Changes are not very noticeable or potential benefits are limited. medium effort Default level of effort must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. testing 🔨
#15670 opened Dec 20, 2024 by cameel
IR codegen does not implement access to library address by contract name bug 🐛 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 eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. should compile without error Error is reported even though it shouldn't. Source is fine.
#15669 opened Dec 20, 2024 by cameel
Inconsistent defaults of optimizeStackAllocation flag cause ICEs and metadata issues in optimized compilation with Yul optimizer disabled 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
#15641 opened Dec 12, 2024 by P1umH0
Bump evmone to 0.13.0 and define Osaka as a supported EVM version EOF 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.
#15622 opened Dec 6, 2024 by cameel
Inconsistent Treatment of Storage Arrays on the Slot Overflow Boundary bug 🐛 low impact Changes are not very noticeable or potential benefits are limited. medium effort Default level of effort must have Something we consider an essential part of Solidity 1.0.
#15587 opened Nov 25, 2024 by ekpyron
Error message "Internal or recursive type is not allowed for public state variables" causes confusion bug 🐛 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 eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. should report better error Error is just badly reported. Should be a proper type error - source is not fine.
#15583 opened Nov 22, 2024 by haoyang9804
ProTip! Updated in the last three days: updated:>2024-12-19.