Tracking Issue for wasi_ext
#71213
Labels
B-unstable
Blocker: Implemented in the nightly compiler and unstable.
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
Libs-Tracked
Libs issues that are tracked on the team's project board.
O-wasm
Target: WASM (WebAssembly), http://webassembly.org/
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Comments
coolreader18
added
the
C-tracking-issue
jonas-schievink
added
B-unstable
KodrAus
added
the
Libs-Tracked
JohnTitor
added a commit
to JohnTitor/rust
that referenced
this issue
Jul 15, 2021
… r=dtolnay Add tracking issue number to `wasi_ext` Feature `wasi_ext` is tracked by rust-lang#71213 but is was not in the source code.
JohnTitor
added a commit
to JohnTitor/rust
that referenced
this issue
Jul 15, 2021
… r=dtolnay Add tracking issue number to `wasi_ext` Feature `wasi_ext` is tracked by rust-lang#71213 but is was not in the source code.
JohnTitor
added a commit
to JohnTitor/rust
that referenced
this issue
Jul 15, 2021
… r=dtolnay Add tracking issue number to `wasi_ext` Feature `wasi_ext` is tracked by rust-lang#71213 but is was not in the source code.
seanyoung
added a commit
to seanyoung/inkwell
that referenced
this issue
Sep 24, 2021
`cargo build --target wasm32-wasi --features llvm11-0` fails with:
--> /home/sean/git/inkwell/src/module.rs:601:95
|
601 | pub fn write_bitcode_to_file(&self, file: &File, should_close: bool, unbuffered: bool) -> bool {
| --------------------- ^^^^ expected `bool`, found `()`
| |
| implicitly returns `()` as its body has no tail or `return` expression
Note that as_raw_fd() cannot be used on wasi yet, since this depends on
wasm_ext which is unstable:
rust-lang/rust#71213
Signed-off-by: Sean Young <[email protected]>
|
Does anyone know what the status of this feature is? |
|
I don't think we want to stabilize this feature while WASI is not stable itself. |
This comment was marked as off-topic.
This comment was marked as off-topic.
smoothwork94131
added a commit
to smoothwork94131/inkwell
that referenced
this issue
Oct 8, 2023
`cargo build --target wasm32-wasi --features llvm11-0` fails with:
--> /home/sean/git/inkwell/src/module.rs:601:95
|
601 | pub fn write_bitcode_to_file(&self, file: &File, should_close: bool, unbuffered: bool) -> bool {
| --------------------- ^^^^ expected `bool`, found `()`
| |
| implicitly returns `()` as its body has no tail or `return` expression
Note that as_raw_fd() cannot be used on wasi yet, since this depends on
wasm_ext which is unstable:
rust-lang/rust#71213
Signed-off-by: Sean Young <[email protected]>
Are we talking about WASI 1.0 or including following APIs in WASI specification (which just happened as part of WASI Preview 2)? |
Anselmkiler
added a commit
to Anselmkiler/testGithub
that referenced
this issue
May 20, 2024
`cargo build --target wasm32-wasi --features llvm11-0` fails with:
--> /home/sean/git/inkwell/src/module.rs:601:95
|
601 | pub fn write_bitcode_to_file(&self, file: &File, should_close: bool, unbuffered: bool) -> bool {
| --------------------- ^^^^ expected `bool`, found `()`
| |
| implicitly returns `()` as its body has no tail or `return` expression
Note that as_raw_fd() cannot be used on wasi yet, since this depends on
wasm_ext which is unstable:
rust-lang/rust#71213
Signed-off-by: Sean Young <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The feature gate for the issue is
#![feature(wasi_ext)].About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Unresolved Questions
When should this be stabilized? Is wasi as a specification stable enough for wasi-specific APIs to be included in std?
Implementation history
#59619
The text was updated successfully, but these errors were encountered: