Skip to content

Prevents direct use of host functions via ExportedFunction #2259

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

Merged
merged 4 commits into from
Jun 20, 2024

Conversation

mathetake
Copy link
Member

@mathetake mathetake commented Jun 20, 2024

I was under the impression that this was already written in the doc
somewhere, but turned out it wasn't. Thank you for reporting @asubiotto

fixes #2257

Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
@mathetake
Copy link
Member Author

I will follow up in a separate PR to enforce this with panic.

Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
@mathetake
Copy link
Member Author

I went ahead and implemented the enforcement of the rule

@mathetake mathetake changed the title doc: adds a note on direct use of host functions Prevents direct use of host functions via ExportedFunction Jun 20, 2024
Copy link
Contributor

@evacchi evacchi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit, otherwise 👍

@mathetake
Copy link
Member Author

tests failing hah

Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
@mathetake mathetake merged commit 69c78f9 into main Jun 20, 2024
58 checks passed
@mathetake mathetake deleted the dochostmodule branch June 20, 2024 16:35
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.

Panic when calling ExportedFunction with WASI function name
2 participants