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
33 Open 24 Closed
33 Open 24 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

Performance improvements of individual Yul Optimizer steps 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. optimizer performance 🐎 selected for development It's on our short-term development
#15508 opened Oct 11, 2024 by cameel
3 of 4 tasks
@cameel
4
Promote custom errors to proper types. 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 selected for development It's on our short-term development
#15388 opened Sep 2, 2024 by ekpyron 0.8.30
Refine and Stabilize EOF Support EOF epic 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. selected for development It's on our short-term development
#15310 opened Jul 31, 2024 by ekpyron
3 of 71 tasks
12
Extremely long running time when emitting irOptimized for AAVE 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 Something we consider an essential part of Solidity 1.0. optimizer performance 🐎
#15141 opened May 23, 2024 by hedgar2017
@cameel
4
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
1
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
try/catch only catches the very first external call feature 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 Something we consider an essential part of Solidity 1.0.
#14080 opened Mar 29, 2023 by 0xdavinchee
4
[SMTChecker] Buggy invariants bug 🐛 high effort A lot to implement but still doable by a single person. The task is large or difficult. smt
#13937 opened Feb 6, 2023 by leonardoalt
2
Unable to use try/catch to catch local reverts in extra code generated for high-level external calls 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. language design :rage4: Any changes to the language, e.g. new features must have Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#13869 opened Jan 12, 2023 by drortirosh
8
Data locations should be tied to types, not variable declarations. 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. needs design The proposal is too vague to be implemented right away roadmap
#13730 opened Nov 21, 2022 by k06a
3
Add support for calldata input and output in abi.decode() high effort A lot to implement but still doable by a single person. The task is large or difficult. language design :rage4: Any changes to the language, e.g. new features 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.
#13518 opened Sep 12, 2022 by k06a
24
Immutable Reference Types breaking change ⚠️ 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. roadmap selected for development It's on our short-term development
#13323 opened Jul 28, 2022 by nishant-sachdeva
3 tasks
2
Functions that are generic in the data location of pointer arguments 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. language design :rage4: Any changes to the language, e.g. new features needs design The proposal is too vague to be implemented right away selected for development It's on our short-term development
#13207 opened Jun 24, 2022 by frangio
1
[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
Optimize ternary expressions to branchless code when cheaper. 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 Something we consider an essential part of Solidity 1.0. optimizer
#12930 opened Apr 13, 2022 by transmissions11
5
Overhaul Inheritance and Override Logic annoys users 😢 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. language design :rage4: Any changes to the language, e.g. new features must have Something we consider an essential part of Solidity 1.0.
#12665 opened Feb 14, 2022 by ekpyron
2 tasks
4
Immutable dynamic arrays 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. language design :rage4: Any changes to the language, e.g. new features selected for development It's on our short-term development
#12587 opened Jan 26, 2022 by nventuro
44
Compiler refuses to generate a getter if omitting struct fields would leave a nested struct empty bug 🐛 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 Something we consider an essential part of Solidity 1.0. should compile without error Error is reported even though it shouldn't. Source is fine.
#12385 opened Dec 8, 2021 by cameel
2
Inline functions / closures / lambdas 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. language design :rage4: Any changes to the language, e.g. new features 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
#12297 opened Nov 19, 2021 by chriseth
3
Support Apple Silicon in Release Builds build system 🏗️ 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 Something we consider an essential part of Solidity 1.0. solcbin
#12291 opened Nov 16, 2021 by xanderdunn
29
try/catch doesn't catch reverts during decoding or inside the try block 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. language design :rage4: Any changes to the language, e.g. new features must have Something we consider an essential part of Solidity 1.0.
#11886 opened Sep 2, 2021 by drortirosh
11
Array literals should be convertible to both dynamically-sized and statically-sized arrays annoys users 😢 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. language design :rage4: Any changes to the language, e.g. new features selected for development It's on our short-term development
#11879 opened Sep 1, 2021 by chriseth
1
@wechman
27
View-pure checker misses reads from storage pointer variable bug 🐛 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 Something we consider an essential part of Solidity 1.0. should report error Compiles without errors but should not.
#11573 opened Jun 23, 2021 by chriseth
@chriseth
4
ARM builds for Linux build system 🏗️ 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. outsourceable Needs little knowledge about the code base and can be done by externals. solcbin
#11351 opened May 5, 2021 by alcuadrado
1
12
try/catch for custom errors 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. language design :rage4: Any changes to the language, e.g. new features must have Something we consider an essential part of Solidity 1.0. needs design The proposal is too vague to be implemented right away
#11278 opened Apr 21, 2021 by hrkrshnn
15
ProTip! Exclude everything labeled bug with -label:bug.