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

Don't Eval.eval in existing module #10

Merged
merged 3 commits into from
Aug 18, 2015
Merged

Don't Eval.eval in existing module #10

merged 3 commits into from
Aug 18, 2015

Conversation

lukewagner
Copy link
Member

Currently Eval.eval evaluates expressions inside the current wasm module (kinda like a JS direct eval) which feels like it violates module encapsulation invariants. This patch mocks up a dummy module.

@lukewagner lukewagner changed the title Don't Eval.eval into existing module Don't Eval.eval in existing module Aug 18, 2015
rossberg added a commit that referenced this pull request Aug 18, 2015
Don't Eval.eval in existing module
@rossberg rossberg merged commit bbe3028 into master Aug 18, 2015
@lukewagner lukewagner deleted the tidy-eval branch August 18, 2015 20:13
@lukewagner
Copy link
Member Author

Thanks for fixing the nits and merging. I was pulled away by a meeting or I would've done it for you; happy to learn the right ML style.

dhil pushed a commit to dhil/webassembly-spec that referenced this pull request Apr 26, 2018
rossberg referenced this pull request in effect-handlers/wasm-spec Feb 15, 2021
dhil pushed a commit to dhil/webassembly-spec that referenced this pull request Mar 2, 2023
Add cont.bind; check handler types
dhil added a commit to dhil/webassembly-spec that referenced this pull request Oct 20, 2023
rossberg pushed a commit that referenced this pull request Mar 7, 2024
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