Marcin Kolny

Yes, I think we'll either have to propose a new version of the C API that adds support for debugging, or have extra API for WAMR headers. I think updating...

Thanks @ricochet / @woodsmc ! > Maintainers (including @sunfishcode ) are aligned with this plan and agree we should continue supporting WASIP1. Sounds good. Once we'll have a formal agreement,...

Hi all, This is the summary of the discussion in this ticket and in the WASI CG meeting we had last week. The community acknowledges the need of supporting preview1...

I personally like the idea of having an error code consistency across runtimes/platforms, as that truly enables us to "write once, run everywhere" in the WASI world. Whereas there are...

I think it'd be helpful for projects that continue using wasi threads with preview 2.

Based on the PR there's some ambiguity around naming nad potential other concerns; I'm going to prepare a few slides and discuss the concerns with the WASI subgroup in the...

@sbc100 thanks for the comment. I agree that doesn't block any of the development, but it might slightly improve development experience as well (e.g. https://github.com/WebAssembly/wasi-libc/issues/156). Given there are no objections,...

@trcrsired what's the status of the work? I seriously consider using wasm64 in one of my projects as that'd solve a few problems; if the work is abandoned, I'm happy...

Since there wasn't any progress on that PR for the last 1.5 month, I'm planning to close on the discussion and finalize the PR. I've requested a slot in the...

> But has there been any discussion of whether this is something we want to officially support in WASI contexts? No, there wasn't any discussion other than https://github.com/WebAssembly/wasi-threads/issues/12 I'm happy...