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.

Sign up for GitHub

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

Jump to bottom

Provide WASI imports when invoking an explicit export from the CLI #2698

Merged
merged 1 commit into from
Nov 30, 2021
Merged

Provide WASI imports when invoking an explicit export from the CLI #2698

merged 1 commit into from
Nov 30, 2021

Conversation

Amanieu
Copy link
Contributor

@Amanieu Amanieu commented Nov 30, 2021

Also calls the _initialize export on a module if it is present, prior to invoking the chosen function (or _start if none is specified).

Fixes #2610

@Amanieu
Copy link
Contributor Author

Amanieu commented Nov 30, 2021

bors r+

@bors
Copy link
Contributor

bors bot commented Nov 30, 2021

Build succeeded:

@bors bors bot merged commit d1cba05 into master Nov 30, 2021
@bors bors bot deleted the wasi_invoke branch November 30, 2021 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@syrusakbary syrusakbary syrusakbary approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

CLI: Allow mixing WASI, implicit/explicit start functions and multiple --invoke?
2 participants
@Amanieu @syrusakbary