Repository navigation
docs: Rust core port plan — decompose #6 into actionable sub-issues - #31
Merged
Merged
Conversation
since the initial audit. Daunting to start in that shape — anyone picking it up has to make a dozen architectural decisions before writing any code. This commit adds docs/rust-core-port-plan.md with: - Scope (what ships in Rust, what stays in TS) - Rollout decision options (big-bang vs parallel-with-flag vs per-function migration) with a recommendation - FFI tooling decision options for native (UniFFI vs JSI direct vs Turbo Modules) and for web (wasm-bindgen as the de facto choice) - Cross-impl conformance testing strategy — re-use the 168 tests from #16 against both impls as the safety net - Native build integration sketch (Expo config plugin + react-native fallback for bare RN consumers) - A decomposition into 14 sub-issues (2 L, 5 M, 7 S) in rough dependency order, with brief scope per sub-issue - Six open architectural questions for the maintainer to decide before any of the sub-issues get filed - What was deliberately NOT included (bytecode cache, streaming parse, persistent storage, multi-canvas state — all real ideas, none belonging in #6) Once the maintainer signs off on the open questions, the 14 sub-issues land on the project board and #6 becomes an umbrella tracker. Until then, this doc is the conversation starter — not a commitment to start coding. README's Development section gains a brief "Strategic direction" subsection pointing at the plan and the umbrella issue, so anyone landing on the README sees the trajectory without having to dig. No code changes. Library checks (38/38 tests, typecheck clean, lint exit 0) pass on this branch as expected. Refs: #6 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
LeslieOA
force-pushed
the
docs/rust-core-port-plan
branch
from
October 4, 2026 20:10
895300a to
bca9292
Compare
Review of #31 before landing. The plan dates from May: - It counted "168 tests" added by #29 as the contract. #29 was closed; the conformance tests landed as #67, #68 and #82, and only the src/core suites test code the port would replace. - It predates src/gtk. The GTK renderer stays TypeScript too, and would load the wasm build, as the README paragraph already says. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ered Leslie's call: land the plan document, but don't announce a Rust direction in the README while the plan itself calls it undecided. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
docs/rust-core-port-plan.md: a plan for #6, with six open questions and a proposed split into 14 sub-issues. It is not a commitment to start; nothing is filed until the questions are answered.The six open questions
Changed in review
src/coresuites cover code the port would replace.src/gtk. The GTK renderer stays TypeScript too and would load the wasm build.Verification
Docs only.
npm test,npm run typecheckandnpm run lintpass.Refs #6
🤖 Generated with Claude Code