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
42 Open 203 Closed
42 Open 203 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
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

High-Level Language Support for Transient Storage epic effort Multi-stage task that may require coordination between team members across multiple PRs. high impact Changes are very prominent and affect users or the project in a major way. selected for development It's on our short-term development
#15007 opened Apr 10, 2024 by ekpyron
Experimental Solidity codegen for types of different stack sizes. experimental high effort A lot to implement but still doable by a single person. The task is large or difficult. high impact Changes are very prominent and affect users or the project in a major way. must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.
#14569 opened Sep 19, 2023 by ekpyron
1
@r0qs
6
Option to harden the Yul optimizer against AST-ID based non-determinism. must have Something we consider an essential part of Solidity 1.0.
#14535 opened Sep 5, 2023 by ekpyron
1
Syntactic call graph as basis for type inference experimental selected for development It's on our short-term development
#14532 opened Sep 4, 2023 by ekpyron
1
@nikola-matic
1
Investigate effects of disabling libevmasm CSE after the Yul optimizer. medium effort Default level of effort medium impact Default level of impact optimizer selected for development It's on our short-term development
#14476 opened Aug 7, 2023 by ekpyron
@matheusaaguiar
2
Change the stack representation of the selector in external function pointers (left-aligned or packed) breaking change ⚠️ low impact Changes are not very noticeable or potential benefits are limited. medium difficulty 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.
#14463 opened Aug 2, 2023 by ekpyron
2
Warning about evaluation order dependent contract creation. medium effort Default level of effort medium impact Default level of impact must have Something we consider an essential part of Solidity 1.0.
#14459 opened Jul 31, 2023 by ekpyron
Further improve stack shuffling performance. selected for development It's on our short-term development
#14343 opened Jun 21, 2023 by ekpyron
@r0qs
2
Type Inference/Checking for Experimental Solidity epic experimental roadmap
#14284 opened May 31, 2023 by ekpyron
2 of 14 tasks
@ekpyron
Lift restrictions on immutables. 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.
#14240 opened May 17, 2023 by ekpyron
1
[experimental] Postfix types. experimental selected for development It's on our short-term development
#14237 opened May 17, 2023 by ekpyron
5 tasks
@ekpyron
JSON Schemata for AST (and potentially all json involved in the compilation process) feature high impact Changes are very prominent and affect users or the project in a major way. 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.
#14141 opened Apr 19, 2023 by ekpyron
Full account of comments in the AST 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. selected for development It's on our short-term development
#13865 opened Jan 11, 2023 by ekpyron 0.8.27
@aarlt
2
verbatim and control flow side effects 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
#13859 opened Jan 10, 2023 by ekpyron
1
Deprecate the use of contractdata as identifier 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
#13800 opened Dec 12, 2022 by ekpyron
Backtracking in the Yul optimizer epic effort Multi-stage task that may require coordination between team members across multiple PRs. epic must have Something we consider an essential part of Solidity 1.0. optimizer viair
#13789 opened Dec 7, 2022 by ekpyron
Contract/Remove CLI options like --yul, --assemble and --strict-assembly 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.
#13714 opened Nov 17, 2022 by ekpyron
Document oddities in validation behaviour of calldata-to-memory copies. documentation 📖 medium effort Default level of effort medium impact Default level of impact must have Something we consider an essential part of Solidity 1.0.
#13520 opened Sep 13, 2022 by ekpyron
1
Type-Checking for code data location. breaking change ⚠️ has dependencies The PR depends on other PRs that must be merged first high impact Changes are very prominent and affect users or the project in a major way. medium effort Default level of effort roadmap selected for development It's on our short-term development
#13369 opened Aug 9, 2022 by ekpyron
3
Add parser support for code data location. breaking change ⚠️ high impact Changes are very prominent and affect users or the project in a major way. medium effort Default level of effort roadmap selected for development It's on our short-term development
#13368 opened Aug 9, 2022 by ekpyron
9
Disallow complex expressions on left-hand-sides of assignments. breaking change ⚠️ 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. needs design The proposal is too vague to be implemented right away
#13147 opened Jun 15, 2022 by ekpyron
3
[Yul Optimizer] Extend LoadResolver to assume zeroed storage during creation code. (And zeroed memory at transaction start.) challenging difficulty high effort A lot to implement but still doable by a single person. The task is large or difficult. high impact Changes are very prominent and affect users or the project in a major way. must have eventually Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it. optimizer
#13099 opened Jun 7, 2022 by ekpyron
2 tasks
1
Yul Optimizer: Switch elimination for cheap switch cases. 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. optimizer
#12931 opened Apr 13, 2022 by ekpyron
1
The optimizer may completely remove all memoryguards preventing stack-to-memory. bug 🐛 medium effort Default level of effort medium impact Default level of impact optimizer
#12913 opened Apr 8, 2022 by ekpyron
Natspec parsing of custom tags always expects a value potentially swallowing other tags. 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.
#12732 opened Mar 2, 2022 by ekpyron
ProTip! Add no:assignee to see everything that’s not assigned.