chriseth
chriseth
Solidity should support template types / generics for contracts, libraries, functions and structs. The syntax should be as follows: ``` library listImpl[T] { struct List { T[] elements } function...
``and(shl(A, X), shl(A, Y))`` should be optimized to ``shl(A, and(X, Y))`` or even ``and(shl(Z, X), shl(Z, Y))`` should be optimized to ``shl(Z, and(X, Y))``
I tried but failed. Assigning to @ekpyron ~Depends on https://github.com/ethereum/solidity/pull/12759 and https://github.com/ethereum/solidity/pull/12795~
This is a story that already exists is pivotal tracker. Solidity should support sum datatype similar to how they are supported by rust. ``` // Enum holding additional data (marked...
Allow function call option on `.transfer` and also `{gas: max}` as a special function call option
This would allow `msg.sender.transfer{gas: max}(2 ether);`, which would then be the recommended way to implement the withdraw pattern.
It is impossible to define multiple events with the same signature in the same contract. This lead to the design that the user documentation ("NatSpec") has a mapping of event...
@alcuadrado and others proposed to expose the boundary between code and data in the emitted bytecode ( https://www.notion.so/Miscellaneous-debugging-symbols-Initial-proposal-2948f1a1f74742c0901ad54af05fa1ff ). I think this is a good idea, but we should not...
The Scoper now does most of the work of the DeclarationRegistrationHelper - we should remove the asserts in the latter and make its behaviour rely on the ground work done...
This is currently a brainstorming issue. ENS should be better integrated into Solidity, but we probably do not want the compiler to make any name lookups at compilation time. Something...
In order to at least somewhat support ENS (we cannot fully support it because that creates issues with source verification), we could have compile-time evaluation of the namehash function on...