We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
foreign
This work likely won't be done until our module system rewrite. This is what declaring foreign values would look like:
@externalName("wasi_unstable") foreign module WasiUnstable { @externalName("fd_write") let fdWrite: annotation ... }
In the future when toplevel wasm imports exist, they would use the toplevel foreign keyword, similar to how it is done now.
The text was updated successfully, but these errors were encountered:
ospencer
alex-snezhko
Successfully merging a pull request may close this issue.
This work likely won't be done until our module system rewrite. This is what declaring foreign values would look like:
In the future when toplevel wasm imports exist, they would use the toplevel
foreign
keyword, similar to how it is done now.The text was updated successfully, but these errors were encountered: