ltzmaxwell
ltzmaxwell
In a simplified scenario to replicate the issue, found that the `long` package path is referenced multiple times when setting objects for storage. The resulting increase in gas consumption `just...
Update: A simple solution could be to use a fixed-length pkgpath, such as `gno.land/p/.....foo.Bar`. However, I'm questioning whether this is worthwhile, as this issue isn't technically a bug.
I don't have a good solution for now, please pick it if you want, sorry for the delay. @leohhhn @r3v4s
> This might be solvable by adding some logic in transcribe, without a dependency graph. > > This might be a better place than transcribe. > > ```go > var...
> The following recursive case is not detected: > > ```go > package main > > type S struct { > A []F > } > > type F func()*S...
this PR is updated: 1. Conduct the check in the preprocessing stage, more specifically, when predefineNow2. The advantage of this approach is that it allows checks to be performed at...
> @ltzmaxwell the code looks goods and testing cases are well defined. > > Have we considered this cyclic dependency case? The Go compiler caught it. > > ``` >...
- The direct cause of this issue is : `Uverse()` generates an incomplete `uverseValue`, which persists unchanged and is globally utilized. - In this particular scenario, `BenchmarkPreprocess` initiates `preprocess`, which...
Hi @moul , Can you give a bit more about this : > similar to how Etherscan can display the last values Thank you!
something related https://github.com/gnolang/gno/pull/319/files