Skip to content

docs: clarify supported wasm scope - #60

Closed
CheckPickerUpper wants to merge 1 commit into
developmentfrom
codex/issue-55-scope
Closed

CheckPickerUpper wants to merge 1 commit into
developmentfrom
codex/issue-55-scope

Conversation

@CheckPickerUpper

Copy link
Copy Markdown
Owner

Linked issue

Closes #55

Observable behavior

The README now describes bulk memory and passive data segments once as supported, distinguishes passive data from unsupported passive element segments, and labels the current i64 behavior as an approximation.

Proof

  • cargo +stable fmt --check
  • cargo +stable clippy --all-targets --all-features --locked -- -D warnings
  • LUAU_BIN=... LUAU_ANALYZE_BIN=... LUAU_COMPILE_BIN=... cargo +stable test --all-targets --locked

@github-actions

github-actions Bot commented Aug 25, 2026 •

Copy link
Copy Markdown

Visual recap — skipped

The visual recap job did not run for this pull request. This is informational only and does not block the PR.

Recap skipped for 7723440: closed without merge.

@CheckPickerUpper

Copy link
Copy Markdown
Owner Author

Superseded by #62; the issue remains open through the accepted scope PR.

@CheckPickerUpper
CheckPickerUpper deleted the codex/issue-55-scope branch August 25, 2026 22:13
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.

Documented scope contradicts itself on bulk memory support

1 participant