feat(text): move shaping and render planning into Rust - #47
Open
thejustinwalsh wants to merge 128 commits into
Open
feat(text): move shaping and render planning into Rust#47thejustinwalsh wants to merge 128 commits into
thejustinwalsh wants to merge 128 commits into
Conversation
size-limit report 📦
|
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
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.
What changed
Why
The shaping and layout state machine must be reusable outside JavaScript, execute through one authoritative boundary, and publish incremental renderer work without reconstructing layout state in adapters.
Evidence
mise exec -- pnpm checkpasses on the final implementation commitfeat/three-apiFollow-ons
Paragraph-scoped synchronous query/candidate adoption and the broader realtime publishing typography set remain separate roadmap items 11.17 and 11.18 so this foundation can merge cleanly first.