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

EOF Source Locations ethdebug feature
#15978 opened Apr 3, 2025 by veniger
2 tasks
Mask generation optimization feature 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
#15870 opened Feb 16, 2025 by moh-eulith
Optimize type(uint256).max into PUSH0 NOT feature optimizer waiting for more input Issues waiting for more input by the reporter
#15761 opened Jan 23, 2025 by radeksvarz
Support for arbitrary contract storage base location feature high impact Changes are very prominent and affect users or the project in a major way. medium effort Default level of effort selected for development It's on our short-term development
#15727 opened Jan 17, 2025 by matheusaaguiar
Generic way to access the underlying type of an UDVT feature 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.
#15318 opened Aug 8, 2024 by aathan
Signed int256 addition optimization 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 selected for development It's on our short-term development
#15283 opened Jul 19, 2024 by Czar102
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
Outputting the CBOR Metadata positions in the bytecode feature 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.
#14827 opened Jan 31, 2024 by kuzdogan
Selective function inlining and optimisation feature must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#14789 opened Jan 19, 2024 by PetarMax
ProTip! Find all open issues with in progress development work with linked:pr.