Repository navigation
analyze: prove document offsets past a non-ASCII character - #5
Merged
Merged
Conversation
Every html/markdown offset assertion added with analyze() was ASCII-only, so none of them discriminated a code-point document offset from a byte one through the span adapters — the place a byte-oriented runtime actually gets it wrong. This runtime is not byte-oriented, but the five ports share one proof set. `café` in the first span puts the UTF-8 byte offset one ahead of the code-point offset, and the test now asserts both numbers rather than only the one it wants. Test-only. 18 analyze tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 18, 2026
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.
Test-only, closing a proof gap left by #4, in parallel with polytypo/polytypo-js#14.
Every
html/markdownoffset assertion that landed withanalyze()was ASCII-only, in all five runtimes — so none of them separated a code-point document offset from a byte one through the span adapters, which is where a byte-oriented runtime would get it wrong. Python is not byte-oriented and the code is right; the five ports share one proof set, so the assertion should discriminate here too.caféin the first span puts the UTF-8 byte offset one ahead of the code-point offset, and the test asserts both numbers.Checks: 18 analyze tests pass, ruff clean.
🤖 Generated with Claude Code