piux2
piux2
GetCallerAt(x) could easily introduce bugs to people who program in gnolang. It is also hard for people to audit the contract. For example, we use GetCallerAt(2) in many example contracts...
Closing this, here is a better solution: https://github.com/gnolang/gno/pull/1315
@ltzmaxwell can you check, do we have some over lapping work with #1141 #1246 #1143? thanks!
> > @ltzmaxwell can you check, do we have some over lapping work with #1141 #1246 #1143? thanks! > > Hey @piux2 , I think they have different intentions, that...
> This is all a bit weird to me and I am not entirely sure the changes you've made go in the right direction. > > Let me try to...
> > it seems that a considerable amount of the lost optimisations are due to the `overflow` checks which are now in place in the `gas` package. > > Are...
I don’t see we need to relate the prevRealm() with IsOriginCall() on the Frame. On chain VM runtim, the calls are initiated from user EOA account to the realm function...
> This PR is essential for the upcoming gnochess event. > > @tbruyelle, could you please focus on reducing the substantial changes, which currently amount to 600k lines? > >...
> **Proposal:** I suggest renaming `std.IsOriginCaller` to `std.IsEntrypoint` to align with the "Main Guard" pattern in Python, preserving the `frames[2]` check. > > ```python > if __name__ == "__main__": >...