Alex Beregszaszi

This came up again as a discussion with @federicobond and I think a good middle ground could be to have an annotation (as proposed in https://github.com/ethereum/solidity/issues/597#issuecomment-221611370), but instead of marking...

There was also a lengthy related discussion in #4017.

Copying the suggestion from @dominicletz from #7593: > A new keyword `fixed(@N)` is proposed that can be used to define fixed slot position in interfaces. > > ``` > interface...

> Are you saying that you would like to add a new method for .call.value()("") (since that syntax is kind of ugly)? We are actually discussing new syntax for that...

A relevant read on the topic: https://diligence.consensys.net/blog/2019/09/stop-using-soliditys-transfer-now/ Given the date on it, it may have been the inspiration for this issue. Two more length articles: - https://ethereum.stackexchange.com/a/38642 - https://github.com/fravoll/solidity-patterns/blob/master/docs/secure_ether_transfer.md

Do we have comparison operators on the contract type (i.e. `Test == Derived` or `type(a) != type(b)`)? There I think `!=` and `==` can make sense, but I agree that...

> With != and == it's not so clear but I would also be in favor of disallowing it. The following may be a reason to disallow it: does it...

@lukewagner would there be a way to refer to WebAssembly exports with an index? That could simplify this.

Good catch, the coinbase does not need to be actually payable, since the "coinbase transaction" is not executing any code.

> Good catch, the coinbase does not need to be actually payable, since the "coinbase transaction" is not executing any code. This still holds. Even staking withdrawals follow the same...