Search results

Straightforward cases where memory mover fails to move enough variables to memory

bug 🐛

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

optimizer

Status: Open.

#16209 In argotorg/solidity;

· cameel opened on Sep 24, 2025

1 comment

Performance improvements of individual Yul Optimizer steps

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

optimizer

performance 🐎

selected for developmentIt's on our short-term developmentIt's on our short-term development

Status: Open.

#15508 In argotorg/solidity;

· cameel opened on Oct 11, 2024

4 comments



Promote custom errors to proper types.

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

medium impactDefault level of impactDefault level of impact

selected for developmentIt's on our short-term developmentIt's on our short-term development

Status: Open.

#15388 In argotorg/solidity;

· ekpyron opened on Sep 2, 2024

· 

0.8.30

Refine and Stabilize EOF Support

EOF

epic

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

selected for developmentIt's on our short-term developmentIt's on our short-term development

Status: Open.

#15310 In argotorg/solidity;

· ekpyron opened on Jul 31, 2024

12 comments

Extremely long running time when emitting irOptimized for AAVE

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

optimizer

performance 🐎

Status: Open.

#15141 In argotorg/solidity;

· hedgar2017 opened on May 23, 2024

4 comments



Resuming compilation from AST import does not produce identical metadata

feature

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

medium impactDefault level of impactDefault level of impact

must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.

Status: Open.

#14986 In argotorg/solidity;

· Subway2023 opened on Apr 4, 2024

1 comment

Experimental Solidity codegen for types of different stack sizes.

experimental

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.

Status: Open.

#14569 In argotorg/solidity;

· ekpyron opened on Sep 19, 2023

1

6 comments



try/catch only catches the very first external call

feature

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

Status: Open.

#14080 In argotorg/solidity;

· 0xdavinchee opened on Mar 29, 2023

5 comments

[SMTChecker] Buggy invariants

bug 🐛

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

smt

Status: Open.

#13937 In argotorg/solidity;

· leonardoalt opened on Feb 6, 2023

2 comments

Unable to use try/catch to catch local reverts in extra code generated for high-level external calls

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

needs designThe proposal is too vague to be implemented right awayThe proposal is too vague to be implemented right away

Status: Open.

#13869 In argotorg/solidity;

· drortirosh opened on Jan 12, 2023

8 comments

Data locations should be tied to types, not variable declarations.

challenging difficulty

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

needs designThe proposal is too vague to be implemented right awayThe proposal is too vague to be implemented right away

roadmap

Status: Open.

#13730 In argotorg/solidity;

· k06a opened on Nov 21, 2022

5 comments

Add support for calldata input and output in abi.decode()

high effortA lot to implement but still doable by a single person. The task is large or difficult.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 featuresAny changes to the language, e.g. new features

low impactChanges are not very noticeable or potential benefits are limited.Changes are not very noticeable or potential benefits are limited.

must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.

Status: Open.

#13518 In argotorg/solidity;

· k06a opened on Sep 12, 2022

24 comments

Functions that are generic in the data location of pointer arguments

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

needs designThe proposal is too vague to be implemented right awayThe proposal is too vague to be implemented right away

selected for developmentIt's on our short-term developmentIt's on our short-term development

Status: Open.

#13207 In argotorg/solidity;

· frangio opened on Jun 24, 2022

1 comment

[Yul Optimizer] Extend LoadResolver to assume zeroed storage during creation code. (And zeroed memory at transaction start.)

challenging difficulty

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.

optimizer

Status: Open.

#13099 In argotorg/solidity;

· ekpyron opened on Jun 7, 2022

1 comment

Optimize ternary expressions to branchless code when cheaper.

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

optimizer

Status: Open.

#12930 In argotorg/solidity;

· transmissions11 opened on Apr 13, 2022

5 comments

Overhaul Inheritance and Override Logic

annoys users 😢

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

Status: Open.

#12665 In argotorg/solidity;

· ekpyron opened on Feb 14, 2022

4 comments

Immutable dynamic arrays

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

selected for developmentIt's on our short-term developmentIt's on our short-term development

Status: Open.

#12587 In argotorg/solidity;

· nventuro opened on Jan 26, 2022

47 comments

Compiler refuses to generate a getter if omitting struct fields would leave a nested struct empty

bug 🐛

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

medium impactDefault level of impactDefault level of impact

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

should compile without errorError is reported even though it shouldn't. Source is fine.Error is reported even though it shouldn't. Source is fine.

Status: Open.

#12385 In argotorg/solidity;

· cameel opened on Dec 8, 2021

2 comments

Inline functions / closures / lambdas

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.

needs designThe proposal is too vague to be implemented right awayThe proposal is too vague to be implemented right away

Status: Open.

#12297 In argotorg/solidity;

· chriseth opened on Nov 19, 2021

3 comments

Support Apple Silicon in Release Builds

build system 🏗️

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

solcbin

Status: Open.

#12291 In argotorg/solidity;

· xanderdunn opened on Nov 16, 2021

29 comments

try/catch doesn't catch reverts during decoding or inside the try block

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

Status: Open.

#11886 In argotorg/solidity;

· drortirosh opened on Sep 2, 2021

11 comments

Array literals should be convertible to both dynamically-sized and statically-sized arrays

annoys users 😢

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

selected for developmentIt's on our short-term developmentIt's on our short-term development

Status: Open.

#11879 In argotorg/solidity;

· chriseth opened on Sep 1, 2021

1

27 comments



View-pure checker misses reads from storage pointer variable

bug 🐛

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

medium impactDefault level of impactDefault level of impact

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

should report errorCompiles without errors but should not.Compiles without errors but should not.

Status: Open.

#11573 In argotorg/solidity;

· chriseth opened on Jun 23, 2021

4 comments



ARM builds for Linux

build system 🏗️

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

must have eventuallySomething we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.Something we consider essential but not enough to prevent us from releasing Solidity 1.0 without it.

outsourceableNeeds little knowledge about the code base and can be done by externals.Needs little knowledge about the code base and can be done by externals.

solcbin

Status: Open.

#11351 In argotorg/solidity;

· alcuadrado opened on May 5, 2021

1

13 comments

try/catch for custom errors

high effortA lot to implement but still doable by a single person. The task is large or difficult.A lot to implement but still doable by a single person. The task is large or difficult.

high impactChanges are very prominent and affect users or the project in a major way.Changes are very prominent and affect users or the project in a major way.

language design Any changes to the language, e.g. new featuresAny changes to the language, e.g. new features

must haveSomething we consider an essential part of Solidity 1.0.Something we consider an essential part of Solidity 1.0.

needs designThe proposal is too vague to be implemented right awayThe proposal is too vague to be implemented right away

Status: Open.

#11278 In argotorg/solidity;

· hrkrshnn opened on Apr 21, 2021

15 comments