Katelyn Gadd

> > Please make UTF-8 the codepage for all shader source. > > Yes, because it makes it so comments can be in any language and we don't have to...

For one example, ECMAScript specifies the valid characters in identifiers pretty concisely: https://262.ecma-international.org/5.1/#sec-7.6  So we could do a stripped down version of that.

It wouldn't need to be interrupted, it would just poll using one of the threading APIs, similar to how a native JIT would do things like on-stack replacement. Right now...

After thinking a bit, perhaps the solution is to not make the value visible to JS, so the thread safety issues are contained to WASM code that can be using...

> Naming nit: if this happens, should we call it a `ProbableUTF8Array` or some such for consistency with existing views? UTF8Array would make sense. If it's 'probable' I think that...

Would it be worthwhile to rough out a proposed API via a polyfill so we can think through some basic issues that way?

It might make sense to initially dictate that it's immutable, i.e. that if you change the heap after allocating it there's no guarantee that the string representation in JS won't...

The immutability isn't enforced by the runtime, it's a promise from the user. So if they violate it there's no guarantee the string will contain what they want. It's just...

You should consider putting a big warning at the top of nuklear.h that says not to edit it. I have another PR in the works I'll have to redo from...

If you manage to reproduce this again, it would be very useful to know the address of the string itself to rule out any alignment issues and to identify whether...