Damian Gryski
Damian Gryski
Try the building with `-tags=osusergo`. But my guess is that you'll hit the same hang (which I think is probably due to a bug in the `interp` pass, which there...
SGTM. We want to keep CI passing.
https://github.com/tinygo-org/tinygo/pull/3191 PR for gc assertions Some of the stats you're looking for might be exposed in the runtime.MemStats struct; but note that 1) it's expensive to call and 2) gcDebug...
Some of the fields in `runtime.MemoryStats` are currently stubbed out; if you need specific fields for debugging, the tracking issue is here: https://github.com/tinygo-org/tinygo/issues/3167
I want to bikeshed the tag. `unknow_wasm` should probaby be `unknown_wasm` at least (to fix the spelling error), but I wonder if we want something like `barewasm` (similar to `baremetal`)...
``` ~/go/src/go.googlesource.com/go/src/compress/flate $ tinygo test compress/flate --dir=. --dir=.. --dir=../.. malformed import path "--dir=.": leading dash malformed import path "--dir=..": leading dash cannot resolve packages: exit status 1 ``` I think...
`--extra-emu-flags=...`
Should we be concerned about the change from `O(1)` to `O(n)` time for tracking allocations?
Fair enough. Let's leave the simple implementation for now and if it becomes an issue we can maybe make a build-tag to drop in a map-based implementation for people who...
If performance is a concern, maybe you shouldn't be using WASM... To be fair, we have the gc disabled for some of our services: `-gc=leaking` is fine for short-lived processes...