Skip to content
New issue

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

WASI-api.md: fix fsync -> fcntl #107

Merged
merged 1 commit into from
Apr 18, 2019
Merged

Conversation

kanaka
Copy link
Contributor

@kanaka kanaka commented Apr 18, 2019

No description provided.

@sunfishcode
Copy link
Member

Good catch!

@sunfishcode sunfishcode merged commit b8fbae2 into bytecodealliance:master Apr 18, 2019
grishasobol pushed a commit to grishasobol/wasmtime that referenced this pull request Nov 29, 2021
pchickey added a commit to pchickey/wasmtime that referenced this pull request May 12, 2023
…tures_drop_cli

drop cli- prefix from reactor, command features & artifact names
pchickey added a commit to pchickey/wasmtime that referenced this pull request May 16, 2023
…tures_drop_cli

drop cli- prefix from reactor, command features & artifact names
frank-emrich pushed a commit to frank-emrich/wasmtime that referenced this pull request Feb 16, 2024
avanhatt pushed a commit to wellesley-prog-sys/wasmtime that referenced this pull request Oct 9, 2024
Introduces an explicit unspecified type in the spec language.

This is motivated by work to model memory operations avanhatt#99, and in
particular the use of the `AMode` enum and its many variants. Some of
the variants are unused at the moment. The unspecified type is intended
to allow us to define _some_ model for them, and therefore satisfy type
inference. However, unspecified type is not allowed to be used for
anything non-trivial, so we would be alerted in future if we need to
revise the model to a correct type.

Updates avanhatt#48 avanhatt#49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants