-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
feat(std/wasi): add return on exit option #8605
Merged
bartlomieju
merged 1 commit into
denoland:master
from
caspervonb:feat-std-wasi-add-exit-on-return-option
Dec 3, 2020
Merged
feat(std/wasi): add return on exit option #8605
bartlomieju
merged 1 commit into
denoland:master
from
caspervonb:feat-std-wasi-add-exit-on-return-option
Dec 3, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bartlomieju
approved these changes
Dec 3, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 21, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 24, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 24, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 24, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 31, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 31, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 31, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Jan 31, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
caspervonb
added a commit
to caspervonb/deno_std
that referenced
this pull request
Feb 1, 2021
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly. Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds an exitOnReturn option to context making it possible to unwind the stack on the exit(2) syscall instead of delegating to it directly.
Node has a similar option, https://nodejs.org/api/wasi.html#wasi_wasi_initialize_instance and my web implementation of WASI unwinds by default.
Use case is being able to treat WASI execution contexts as children that don't kill the parent on exit.