perf: make native text renderer limits observable#1
Open
saseungmin wants to merge 1 commit into
Open
Conversation
The nativeText wrapper is staying in place while normal and stress workloads become easier to judge. This adds the example probe and docs language needed before changing renderer internals. Constraint: nativeText wrapper cost needs evidence before renderer redesign Rejected: Add runtime token caps | no measured threshold yet and DX would suffer Rejected: Start alternate renderer | current visual checks did not show probe issues Confidence: high Scope-risk: moderate Directive: Do not redesign nativeText from stress cases without normal-workload evidence Tested: pnpm run format:check Tested: pnpm run lint Tested: pnpm run typecheck Tested: pnpm run test Tested: pnpm run build Tested: pnpm run example:build Not-tested: Numeric FPS capture with profiler tooling
|
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
Verification
Notes
Numeric FPS capture is still a future manual measurement step; current visual iOS/Android checks showed no obvious jank.