ControlCplusControlV
ControlCplusControlV
@seanmonstar could you elaborate a bit more on why this choice was made? It requires some ugly work around such as ` server: Pin
See #2 as well
Could we maybe squeeze in #3607
payable on everything and throw in non-payable? If not we can continue discussion elsewhere
Have a draft for `block.blobbasefee` on my branch now
I support this a lot, but I have a couple ideas/questions, I am not sure how useful this one would be but having `@reentrant(5)` to allow a specific number of...
> Do you have a specific use case in mind where this would be useful? To be honest I doubt this actually sees much if any use, but think it...
I really like the syntax for that, would support implementing it like that
There is such thing as read-only re-entrancy, wonder if there would be any way to help mitigate that with this
**Dead Memory** If a value is stored in memory, once it's location is never read from again the compiler can consider that memory as "free," and overwrite it **Test Cases**...