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

Immutable variables treated differently depending on type bug πŸ› medium effort Default level of effort medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#15989 opened Apr 8, 2025 by frangio
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
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
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
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
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
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
Document output selection documentation πŸ“– low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#15744 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
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
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
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
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
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
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
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
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
Switch all MacOS scripts to use GNU utils build system πŸ—οΈ 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. refactor
#15401 opened Sep 4, 2024 by nikola-matic
Support "calldata" as an overloaded location for reference variables. feature must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#15000 opened Apr 8, 2024 by Amxx
Resuming compilation from AST import does not produce identical metadata feature high effort A lot to implement but still doable by a single person. The task is large or difficult. medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#14986 opened Apr 4, 2024 by Subway2023
Version the list.json file for build information feature low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. solcbin
#14955 opened Mar 19, 2024 by sambacha
Allow modularising yul assembly feature must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#14855 opened Feb 15, 2024 by zemse
version pragma accepts partial string literals in any position 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.
#14826 opened Jan 31, 2024 by OmarTawfik
SMTChecker support for EIP-6780: SELFDESTRUCT only in same transaction must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. smt
#14804 opened Jan 25, 2024 by r0qs
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.