What's the current status of WASM/WASI support?

[Johan]

On Friday, 3 November 2023 at 23:36:45 UTC, Sebastiaan Koppe 
wrote:
> On Monday, 16 October 2023 at 04:11:19 UTC, redthing1 wrote:
>> On Tuesday, 14 March 2023 at 23:45:12 UTC, ChrisG wrote:
>>> In 2019, there was a blog post that indicated a strong push 
>>> for wasm support was afoot. I've had a hard time pulling 
>>> together information since then. I was curious if anyone has 
>>> a good general perspective on the state of D wasm support. I 
>>> can't tell if it's a mostly dead subject. It looks like 
>>> betterC support is generally there, but I'm not sure about 
>>> runtime or library support. Specifically, I was interested in:
>>>
>>> - What's the runtime support story (can I use GC)?
>>> - What's the phobos support story?
>>> - Are there alternate general purpose libraries folks have 
>>> settled on for wasm development? (spasm?)
>>> - Anything about WASI or Emscripten?
>>>
>>> Thanks.
>>
>> I was wondering actually, has anyone experimented with WASI + 
>> D? I am interested in looking into it.
>
> The d runtime port I did years ago used wasi and the wasi-libc. 
> I ported the whole of druntime (aside from things like catching 
> exception, fibers, etc.) but got stuck on the GC.

It is really a pity that you (or someone else) never upstreamed 
this (or related) work. I feel it is good work going to waste :/
Let's not strive for perfect, strive for improvement. And the 
barrier for improvement is pretty low current with a completely 
non-working druntime with wasm (with or without wasi)...!

The separate minimum druntime work is valuable, but could be much 
more valuable if it became part of the standard druntime.

The WASM work always makes me excited, although I've never used 
it.
Thanks!
   Johan