-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Label
Projects
Milestones
Assignee
Sort
Issues list
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
Builtin for base slot of storage layout
medium effort
Default level of effort
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.
#15903
opened Feb 28, 2025 by
cameel
ExpressionSimplifier references variables declared in loop body when simplifying the post block
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
must have
Something we consider an essential part of Solidity 1.0.
optimizer
#15889
opened Feb 26, 2025 by
lum7na
SMT logic error from incorrect handling of fixed bytes to user defined value type conversion
#15888
opened Feb 25, 2025 by
lum7na
Inconsistent view/pure semantic restrictions related to storage pointers
bug 🐛
#15886
opened Feb 23, 2025 by
Philogy
EthDebug Format Output (Source Maps Equivalent)
ethdebug
feature
selected for development
It's on our short-term development
#15884
opened Feb 21, 2025 by
veniger
Missing bytecode size warnings for EIP-3860 and in Yul/EVM asm mode
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.
#15861
opened Feb 13, 2025 by
cameel
Introduce an exception type for the AST Json importer and use as replacements for 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.
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.
solAsserts
low effort
#15854
opened Feb 12, 2025 by
matheusaaguiar
Consider adding option in isoltest to check for secondary error messages
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.
testing 🔨
#15843
opened Feb 10, 2025 by
matheusaaguiar
Remove the disabled 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.
>>>
(SHR) operator
low effort
#15839
opened Feb 7, 2025 by
cameel
The 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.
experimental
flag in CBOR metadata is not set when targeting experimental EVM versions
bug 🐛
low effort
#15835
opened Feb 6, 2025 by
cameel
Inherited Enum Allows Type Reference but Not Value Access
bug 🐛
#15832
opened Feb 5, 2025 by
zzh1996
Convert 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.
verbatim
into a single builtin with literal arguments
breaking change ⚠️
low effort
Deprecation warnings for features we plan to remove
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
Disallow internal function pointers in storage
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
Something we consider an essential part of Solidity 1.0.
Compilation and Optimizer Performance Improvements
selected for development
It's on our short-term development
#15786
opened Jan 27, 2025 by
ekpyron
Previous Next
ProTip!
Updated in the last three days: updated:>2025-03-02.