Andrew Scheidecker

How about allowing quoted names: `$"arbitrary\00string"`?

> In particular, it would pull in Unicode into a central piece of the text semantics and get us into the business of defining the right equivalence on arbitrary Unicode...

> @AndrewScheidecker, fair enough, but we would still introduce the situation where there are many different ways to spell the same identifier, e.g., using unicode escapes, raw UTF-8 hex escapes,...

Glad to see this discussion. I think that specifying the interaction of the optional features in normative text is really desirable. If the features are just in independent appendices, there...

> I think the reasonableness of this proposal depends in part on the underlying behaviour of OS functions There's [an old thread](https://github.com/WebAssembly/design/pull/1019#issuecomment-291244537) where I raised the issue that wait/wake don't...

I started this issue to suggest switching from option 2 to 1, but now I think it would be best to keep option 2. If something like `mmap` is added...

> It's somewhat consistent with current reality to wake those threads when we shrink the memory, but we'd have to wake them with a result code that we don't currently...

> When we add a more flexible opaque thread type eventually, would we add another `create_thread` instruction? I think you could do this in a forward compatible way by adding...

> I am wondering more about the instruction set. With a more general thread type potentially added later it would be silly to still require a table just to create...

WAVM has some non-standard support for shared instances (and tables) at the C API level. One way that it differs from the shared functions @rossberg is talking about is that...