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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
141 Open 217 Closed
141 Open 217 Closed
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
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

SMTChecker: Some (uncommon) valid values for selecting contracts are rejected as invalid bug 🐛 low impact Changes are not very noticeable or potential benefits are limited. smt
#15945 opened Mar 15, 2025 by blishko
1
Lift restrictions against allocating the last storage slot 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.
#15911 opened Mar 3, 2025 by cameel
3
Missing bytecode size warnings for EIP-3860 and in Yul/EVM asm mode 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. should have We like the idea but it’s not important enough to be a part of the roadmap.
#15861 opened Feb 13, 2025 by cameel
2
Introduce an exception type for the AST Json importer and use as replacements for solAsserts 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.
#15854 opened Feb 12, 2025 by matheusaaguiar
1
Consider adding option in isoltest to check for secondary error messages 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. should have We like the idea but it’s not important enough to be a part of the roadmap. testing 🔨
#15843 opened Feb 10, 2025 by matheusaaguiar
Remove the disabled >>> (SHR) operator 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. should have We like the idea but it’s not important enough to be a part of the roadmap.
#15839 opened Feb 7, 2025 by cameel
1
2
The experimental flag in CBOR metadata is not set when targeting experimental EVM versions 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.
#15835 opened Feb 6, 2025 by cameel
@nikola-matic
3
Convert verbatim into a single builtin with literal arguments breaking change ⚠️ 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.
#15805 opened Jan 31, 2025 by cameel 0.9.0
2
Disallow internal function pointers in storage breaking change ⚠️ 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.
#15794 opened Jan 29, 2025 by cameel 0.9.0
2
Update Code Examples from Using Web3.js to Ethers.js 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. must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#15759 opened Jan 23, 2025 by codersjj
1
1
Inconsistent behavior of * and empty string in outputSelection 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.
#15747 opened Jan 20, 2025 by cameel
Do not assemble deployedObject when not requested 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.
#15746 opened Jan 20, 2025 by cameel
deployedBytecode output is empty in Yul mode for contracts with bytecode dependencies 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.
#15745 opened Jan 20, 2025 by cameel
ICE when inline assembly references a variable that shadows a contract and is nested >256 levels deep 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.
#15739 opened Jan 20, 2025 by Jizhou-Chen
1
Array of super is still accepted as a type in some contexts and triggers and ICE in abi.decode() 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 error Compiles without errors but should not.
#15737 opened Jan 20, 2025 by Jizhou-Chen
1
Named arguments in string.concat() trigger an ICE 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.
#15735 opened Jan 20, 2025 by Jizhou-Chen
1
Bypassing the deployed bytecode with inline assembly in constructor makes it disappear from creation bytecode 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.
#15725 opened Jan 17, 2025 by cameel
@nikola-matic
Inconsistent treatment of constants by static analysis and constant evaluation bug 🐛 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. should compile without error Error is reported even though it shouldn't. Source is fine.
#15709 opened Jan 13, 2025 by blishko
4
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 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 0.8.30
2
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
4
Yul object names with dots are accepted but ambiguous 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.
#15540 opened Oct 23, 2024 by cameel
2
ICE when loading the same file multiple times via import callback 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.
#15458 opened Sep 25, 2024 by cameel
2
do-while results in redundant branching instructions when compiling via IR low impact Changes are not very noticeable or potential benefits are limited. medium effort Default level of effort 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. optimizer
#15442 opened Sep 19, 2024 by Philogy
3
ProTip! Add no:assignee to see everything that’s not assigned.