Adrian Cole

Gotcha, but let me make sure. You have a wasm+wasi runner defined in Go. Right now, it depends on offline compilation of wasm (or forking a tinygo process). You'd prefer...

cool, so I think unless my [technical assessment](https://github.com/tinygo-org/tinygo/issues/2016#issuecomment-1243068938) is off (often is) the runner (wasm host) would import a tinygo library, but in doing so need to somehow get access...

I think this will break a significant amount of the TinyGo wasm community, so this should sit at least a few days to deal with timezones etc.

First, I would like to decouple this from me. I don't actually build end wasm, just I respond to many people who are using tinygo to various levels of success....

#3148 looks like it would remove the safety issues in the built-in "malloc", a primary reason to discourage its use. effectively it changes it from unsafe to safe. So, I...

ps we created a lib which if used can decouple things. since this is integration tested it should be usable regardless of decision here https://github.com/tetratelabs/tinymem/pull/2

@aykevl Thanks for progressing. So if I understand correctly, users won't be able to export via flags to `tinygo build`, rather add this to their main.go before they build it....

As far as I'm concerned the workaround is helpful, if it is planned to stick around. If you think it will be removed later, than maybe still helpful but should...

I can understand where you are coming from. keep in mind that tinygo is for end users, not its developers. Also, as I mentioned, a normal developer would probably use...

@deadprogram and I suppose modifying code is in any case necessary meanwhile, as we have no other way to pass cgo LDFLAGS another way (such as `CGO_LDFLAGS` env variable). Correct?