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
431 Open 5,540 Closed
431 Open 5,540 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

Turn on the optimizer by default breaking change ⚠️ high impact Changes are very prominent and affect users or the project in a major way. low effort There is not much implementation work to be done. The task is very easy or tiny. selected for development It's on our short-term development
#13223 opened Jun 28, 2022 by axic 0.9.0
8 😄 1
payable function modifier documentation not found documentation 📖 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.
#10312 opened Nov 17, 2020 by miohtama
2 😄 1
Allow specifying storage locations 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.
#597 opened May 25, 2016 by pipermerriam
78
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 :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
#869 opened Aug 11, 2016 by chriseth
41
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 :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
#909 opened Aug 16, 2016 by chriseth
14
Introduce a type definition keyword language design :rage4: 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
14
Ranked overload resolution language design :rage4: 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
13
Short notation for function types 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 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
6
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 :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
#2435 opened Jun 21, 2017 by chriseth
11
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
10
Syntax to refer to a specific overload of a function language design :rage4: 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
29
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
7
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
4
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
12
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
4
[SMTChecker] Cleanup warnings and expression undefined low effort There is not much implementation work to be done. The task is very easy or tiny. smt
#5618 opened Dec 10, 2018 by leonardoalt
@pgebal
4
type().max min should work with user defined types that are mapped to scalar types feature
#15318 opened Aug 8, 2024 by aathan
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
19
[SMTChecker] Loop invariants smt
#6210 opened Mar 6, 2019 by leonardoalt
7
[soltest] Incorrect semantics tests suggestions for unaligned hex strings. bug 🐛 testing 🔨
#6703 opened May 8, 2019 by ekpyron
2
[Yul] optimizer's AST copier leaks memory bug 🐛
#6734 opened May 13, 2019 by bshastry
4
abi.decode: function type cannot be decoded bug 🐛 should compile without error Error is reported even though it shouldn't. Source is fine.
#6942 opened Jun 14, 2019 by amkCha
@chriseth
3
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
8
[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
5
SMTChecker: Contract invariants support language design :rage4: 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
15
ProTip! What’s not been updated in a month: updated:<2024-07-09.