dcodeIO

Would this perhaps become simpler if we'd keep tracking such segments as `MemorySegment`s but allowed the buffer to be `null`, indicating all zeroes? More generally, when not indicating the presence...

I am primarily interested in replacing the custom set of non-standard imports AssemblyScript has, like `env.trace`, `env.seed`, `env.time`, etc. with WASI to integrate well with both WASI-enabled hosts and an...

> Logging in general seems straightforward to consider, and separating out functionality like this into modules is something we're already working on. 👍 > Alternatively, is there a way in...

I agree that this is separable, yeah. Regarding your questions, this isn't entirely about performance. I guess the best one could do in their non-UTF-8 language is something like the...

Oh, sorry, didn't want to imply that someone suggested that. It's all fine, appreciate your input 🙂 And yeah, AS does not have a C-like stack (well, technically it has...

AS uses `__data_end`, `__stack_pointer` and `__heap_base`, with a stack growing downwards, similar to LLVM, for the managed shadow stack, yeah. All a bit unfortunate, as the GC is precise and...

The syslog interface looks good to me. Can map well to JS's `debug`, `info`, `warn` and `error` I think. Regarding simple debugging vs logging in production, perhaps both can use...

On the AssemblyScript side, I imagine an explicit `anyref` type that works like any other native Wasm type (very similar to what one would write in wat), plus potentially combining...

Yeah, more statically available information is always better. Wondering how we can provide it, though, given that Wasm modules and Wasm hosts are composable in many ways, so a module...

> 1. Languages where String is not a primitive type, but a subtype of other classes, like Object, would need to have custom fields in String for "type info" or...