-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Remove .send and .transfer.
breaking change ⚠️
high impact
Changes are very prominent and affect users or the project in a major way.
language design
Any changes to the language, e.g. new features
low effort
There is not much implementation work to be done. The task is very easy or tiny.
needs design
The proposal is too vague to be implemented right away
templates / generics
epic effort
Multi-stage task that may require coordination between team members across multiple PRs.
generics
high impact
Changes are very prominent and affect users or the project in a major way.
language design
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
#869
opened Aug 11, 2016 by
chriseth
Remove Any changes to the language, e.g. new features
low effort
There is not much implementation work to be done. The task is very easy or tiny.
medium impact
Default level of impact
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.
uint
as alias for uint256
breaking change ⚠️
feature
language design
Short notation for function types
high impact
Changes are very prominent and affect users or the project in a major way.
language design
Any changes to the language, e.g. new features
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.
needs design
The proposal is too vague to be implemented right away
roadmap
#1349
opened Nov 9, 2016 by
chriseth
Allow specifying storage locations
language design
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.
Enums with data / sum datatype / algebraic datatypes
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
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
#909
opened Aug 16, 2016 by
chriseth
Introduce a type definition keyword
language design
Any changes to the language, e.g. new features
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.
#1100
opened Sep 15, 2016 by
o0ragman0o
Ranked overload resolution
language design
Any changes to the language, e.g. new features
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.
needs design
The proposal is too vague to be implemented right away
#1256
opened Oct 20, 2016 by
chriseth
Make copy / reference semantics more explicit
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.
language design
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
#2435
opened Jun 21, 2017 by
chriseth
Constant expression evaluation at compile time
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.
needs design
The proposal is too vague to be implemented right away
selected for development
It's on our short-term development
#3157
opened Oct 30, 2017 by
axic
Syntax to refer to a specific overload of a function
language design
Any changes to the language, e.g. new features
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.
needs design
The proposal is too vague to be implemented right away
#3556
opened Feb 20, 2018 by
axic
ABI: Event selectors do not distinguish indexed arguments
bug 🐛
protocol design 🔮
Potential changes to ABI, meta data, standard JSON
#4168
opened May 21, 2018 by
frangio
behavior of named arguments in function types
bug 🐛
low impact
Changes are not very noticeable or potential benefits are limited.
medium effort
Default level of effort
#4299
opened Jun 14, 2018 by
ekpyron
Call For Action: standard library for Solidity
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
stdlib
#228
opened Nov 18, 2015 by
axic
SMTChecker: Contract invariants support
language design
Any changes to the language, e.g. new features
medium effort
Default level of effort
medium impact
Default level of impact
needs design
The proposal is too vague to be implemented right away
smt
#4991
opened Sep 17, 2018 by
leonardoalt
Shadowing warning between local variables or function depend on declaration order
bug 🐛
low impact
Changes are not very noticeable or potential benefits are limited.
medium effort
Default level of effort
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.
should report better error
Error is just badly reported. Should be a proper type error - source is not fine.
#5173
opened Oct 9, 2018 by
chriseth
Unable to check existence of precompiled contract by its address or get its code in VM or Sepolia testnet
bug 🐛
#15428
opened Sep 12, 2024 by
amit-supraoracles
Add new external tests
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.
testing 🔨
#5956
opened Feb 7, 2019 by
chriseth
[soltest] Incorrect semantics tests suggestions for unaligned hex strings.
bug 🐛
testing 🔨
#6703
opened May 8, 2019 by
ekpyron
Specification of ABI decoding (especially padding in bytes)
documentation 📖
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.
#6978
opened Jun 20, 2019 by
sifmelcara
[isoltest] Formatting should support strings longer than 32 bytes
bug 🐛
low impact
Changes are not very noticeable or potential benefits are limited.
medium effort
Default level of effort
should compile without error
Error is reported even though it shouldn't. Source is fine.
should have
We like the idea but it’s not important enough to be a part of the roadmap.
testing 🔨
#7197
opened Aug 7, 2019 by
erak
Rethink (or maybe even remove?) Changes are very prominent and affect users or the project in a major way.
language design
Any changes to the language, e.g. new features
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
super
breaking change ⚠️
high impact
#7261
opened Aug 14, 2019 by
ekpyron
Add .exists() and .iscontract() on to the address type
language design
Any changes to the language, e.g. new features
#4910
opened Sep 5, 2018 by
axic
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.