Alex Beregszaszi

Last piece waiting is fixing the patch system for wasm3 or fixing+merging #739.

Well basically `external pure` can have different rules, than `private/public/internal`. We had another issue for tracking the memory-mutability of pure, that should be also revived.

`.exists()` probably should be postponed until there is a consensus on what that means in Ethereum, however when looking at the account cleanup rules during creation/selfdestruct/etc. should be a good...

Actually it seems that `.iscontract()` could be implemented by just using `extcodehash`.

`.exists()` can be clearly implemented post Constantinople, because [EIP-1052](https://eips.ethereum.org/EIPS/eip-1052) for `EXTCODEHASH` clearly defines it: > In case the account does not exist or is empty (as defined by EIP-161) 0...

@frangio @wadeAlexC any change of view since these are provided by opcodes now?

> I don't think that really mitigates the vulnerabilities that can arise from using .isContract(), because an account can pass the EXTCODEHASH test but still become a contract in the...

This would become very useful in conjunction with https://github.com/ethereum/EIPs/pull/8838 On non-EOF targets it could fallback to extcodesize/extcodehash.

A more refined statement would be `import { evmVersion } from solidity;`, but I still think this has to be a special keyword and not a path, because otherwise the...

Not sure I follow the reasoning for why it should be a Yul builtin, but also see this: > Potentially this `solidity` namespace could contain the other native types proposed...