Solidity generates EVM bytecode that leads to an invalid jump destination when:
throw
is used- ... ?
- ... ?
Can the above list be completed, with examples?
To explain the first item, throw
in Solidity source code, gets compiled to EVM bytecode that leads to an invalid jump destination. (Of course it assumes that the throw
is not in dead code that might be optimized away.) What are all the other scenarios that belong in the list?