Damian Gryski

While we're here we should probably update the calls to `ioutil/*` to the appropriate `io` or `os` methods.

Is this documented sufficiently already or do we need to fix it? If the docs are up-to-date, can we close this bug?

This addresses one of the issues preventing the `math/big` tests from running. ( https://github.com/tinygo-org/tinygo/issues/890 )

Ranging over an addressable array as you are doing here causes Go to have to copy the array. You can prevent this by instead ranging over a slice: ``` for...

Good point. Seems like there must be something about how we're generating the IR for this particular case that causes the memory bloat.

Looks like an issue with `interp`.

@dulanov That seems like a different error than the one @dankegel reported.

Easy enough to add some links to the tinygo wasm docs page or equivalent. If it doesn't end up on the tinygo site proper I'm sure we can find some...

Should this pattern be documented somewhere or can we close this bug?

I think @dominikh has looked at data flow analysis for staticcheck.