feat(runtime): Add support for wasm32-wasip2 compilation target
#4058
Conversation
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
…time adjustments Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
|
You're welcome to continue experimenting with this, but there's no point in merging this until it's stabilized as a target for |
Totally fair, I understand it’s still experimental. The WASI Preview 3 target (wasm32-wasip3) is expected to land in the next Rust release or just after that (most probably), but for now I’m using wasm32-wasip2 as the dev target to keep things working. It’s mostly exploratory right now, but it does feel like something that’ll be quite useful once stabilized. |
|
@abonander Would it be alright to keep this PR open as a reference while I continue experimenting, or would you prefer I link to my fork in the relevant issue and close this PR to keep the list clean? |
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
… works, runtime fails at handshake Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
Aditya1404Sal
force-pushed
the
latest/wasip3
branch
from
4afcb31 to
e25f19f
Compare
…mutex lock issue Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
Aditya1404Sal
force-pushed
the
latest/wasip3
branch
from
e25f19f to
a71af8a
Compare
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
Aditya1404Sal
changed the title
wasm32-wasip3 compilation target.]wasm32-wasip2 compilation target
Signed-off-by: Aditya <aditya.salunkh919@gmail.com>
2 participants
Does your PR solve an issue?
closes #4056
Is this a breaking change?
No, New runtime would run separately, conditional compilation ensures that.