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

429 Open 5,542 Closed
429 Open 5,542 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

Remove .send and .transfer. breaking change ⚠️ 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. needs design The proposal is too vague to be implemented right away
#7455 opened Sep 19, 2019 by MicahZoltu 0.9.0
25
Array slices for memory and storage arrays. 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.
#7423 opened Sep 13, 2019 by ekpyron
5
[SMTChecker] Refactor pointers easy difficulty good first issue candidate Could be a "good first issue" but something is blocking it or it has open questions. smt
#7266 opened Aug 15, 2019 by leonardoalt
7
Rethink (or maybe even remove?) super breaking change ⚠️ 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 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
#7261 opened Aug 14, 2019 by ekpyron
17
[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
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
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
[ossfuzz] reproducing use-after-free bug reported by ossfuzz CI on 28.05.19 bug 🐛
#6870 opened May 29, 2019 by bshastry
5
[Yul] optimizer's AST copier leaks memory bug 🐛
#6734 opened May 13, 2019 by bshastry
4
[soltest] Incorrect semantics tests suggestions for unaligned hex strings. bug 🐛 testing 🔨
#6703 opened May 8, 2019 by ekpyron
2
[SMTChecker] Loop invariants smt
#6210 opened Mar 6, 2019 by leonardoalt
7
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
Large StandardCompiler (AST JSON) output cannot be parsed by jsoncpp 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.
#5898 opened Jan 29, 2019 by axic
9
[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
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: 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
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
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
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
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
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
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
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
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
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.