Leo
Leo
Rebased and applied suggestions from @ekpyron .
@cameel question for you /\
Thank you for the PR! Unfortunately review has shown that the PR actually does the opposite of what the compiler is trying to do by design. Therefore, I'm closing it...
Attempt failed. Close?
I think this shouldn't go into the language with `safe/protected` keywords and such, and should rather have similar behavior as checked arithmetic. IMO, reentrancy guards could be added by default...
https://github.com/ethereum/solidity/issues/13124 is a dup of this issue in general but offers two different approaches: - Aggressive: basically what I said above - Conservative: try to detect whether state changes are...
I personally really dislike the idea of function modifiers for reentrancy. It's too binary and does not represent the amount of different use cases. Moreover: - the strategy you mention...
> It will be much easier to implement robust automatic runtime protections against reentrancy attacks at runtime once [EIP-1153](https://eips.ethereum.org/EIPS/eip-1153) is merged, because it will allow for flags to be set...