-
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
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
Add support for A lot to implement but still doable by a single person. The task is large or difficult.
language design
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.
calldata
input and output in abi.decode()
high effort
#13518
opened Sep 12, 2022 by
k06a
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
IPFS hash feature use non-specified algorithm which is not widely compatible in the ecosystem
bug ๐
#14389
opened Jul 8, 2023 by
Jorropo
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
Enough Debugging data for tools to switch to via-IR
epic
ethdebug
roadmap
viair
#13720
opened Nov 17, 2022 by
NunoFilipeSantos
4 of 6 tasks
Should private functions really clash ?
bounty worthy ๐ฐ
help wanted
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.
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.
#11889
opened Sep 3, 2021 by
Amxx
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
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
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
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
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
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
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
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
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
Previous Next
ProTip!
Follow long discussions with comments:>50.