You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
abi_encode/abi_decode function usable within the language, this is frequently used by building data for signature checking (this likely already exists in some form) (see EIP-712, and Solidity's features)
The items I mentioned being important for "early production readiness":
abi_encode/abi_decodefunction usable within the language, this is frequently used by building data for signature checking (this likely already exists in some form) (see EIP-712, and Solidity's features)publicvisibility modifier for contract functions #434)structdata type in memory/ABI (Add Solidity-style structs with named fields and dot access #568)structin storage (Support struct sub-field writes to storage fields #571)Nice to haves:
calldata(bytes))breakin for loops (Implement break in for-loops #488)continuein for loops (Supportcontinueinfor-loops #490)uint256(1234)everywhere)~and~=sugar #536)*=and/=(Add*=and/=compound assignment sugar (and extended tests) #537)<<,>>) -- consider arithmetic vs logicaln ** y)++/--expressions[n:],[n:m],[:m]I think after these it would be possible to accomplish most needs as a user.