Alex Beregszaszi

> While that's very good for our development and CI, this can be annoying for end users and for dependent projects. We should add a CMake option that disables all...

What is the reason to build it themselves, and what reasonable compiler would fail on it?

To provide feedback from another angle: I would find it tiring to move head/eyes 50 centimeters across should it be fully expanded. Yes, I could resize the browser window too,...

Weird that this change mostly increases gas -- or is that only for the isolated test cases and when it is used in the complete optimisation suite it helps?

In fact we already did this 2-3 years ago, when we discussed "Yul++" ([see this hackmd](https://hackmd.io/Hj2z5Rm3Qj-2g8Ct9GOpSQ)) upon prompt by @SilentCicero, which eventually turned into [yulp](https://github.com/FuelLabs/yulp). What other Yul+ do you...

I am leaning towards that constants should be supported in interfaces instead.

@VoR0220 do you think we should close this in favour of #240 which has more details?

Yes, the title should be changed.

Changing the way the constructor works would be a breaking change beyond the compiler/language, but every web3 tool would need to be changed. The reason is the "function signature" is...

That status is still the same as in https://github.com/ethereum/solidity/issues/232#issuecomment-464729858: > Status is "Neither fully specified nor planned".