Skip to content

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
CharlieTap pushed a commit to CharlieTap/spec that referenced this pull request Sep 25, 2025
…rnative

Fill out the alternatives section for overflow flags
stevenfontanella pushed a commit to stevenfontanella/spec that referenced this pull request Nov 12, 2025
spec: e3a3c12
  simd: 6740657c4a88a73046bc982ce4530d83937bf322
  bulk-memory-operations: 77db9426ff00eb7490e39548eb1e907ba98fec45
  nontrapping-float-to-int-conversions: 95b9dffdbb759b0f8de5db4ad23531680da5c123
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.

3 participants