chriseth

We should be careful if non-private can be changed to private in inheritance.

@Amxx can you provide more cases that would benefit from this feature? I actually think @axic 's point is very valid here.

Tracked in https://github.com/ethereum/solidity/issues/7314

This seems to be due to loop-invariant code motion. cc @hrkrshnn Maybe we should not pull out things that are potentially very expensive? On the other hand, the assumption was...

The main problem I see is that tuples are not "proper" types in solidity.

The point is that we do not want to have arbitrary access to tuple elements - the element always has to be a compile-time constant, otherwise code generation gets very...

Especially with contract upgrades in mind, wouldn't it be better to copy the storage layout and "disable" unused state variables by e.g. prefixing them? Otherwise I don't see how you...

http://solidity.readthedocs.io/en/latest/miscellaneous.html#layout-of-state-variables-in-storage

I think the tradeoff between introducing errors and decreasing readability is much better when just adding `int c` at the end. If you want, you can also use inheritance (let...

I really don't think solidity should have such low-level impact on the storage location. If you want to dislocate storage variables, why not use structs or a mapping to structs?