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

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
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
Requesting implicitly generated outputs 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 have We like the idea but itโ€™s not important enough to be a part of the roadmap.
#15742 opened Jan 20, 2025 by cameel
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
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
ProTip! no:milestone will show everything without a milestone.