Conversation
… the file Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
PR summary e019f6fae1Import changes for modified filesNo significant changes to the import graph Import changes for all files
|
This branch has not been deployed
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.
This PR fixes the positions reported by the
linter.style.docStringVersolinter. The linter parses the doc-string text in a fresh input context, so the parse errors carry positions relative to the doc-string, and logging them at the resulting syntax produced line numbers relative to the doc-string rather than the file (this week's weekly linting report has warnings atMathlib/Algebra/Field/GeomSum.lean:3, the copyright header). The linter now offsets each error by the position of the doc-string text in the file and reports the range from the start of the construct Verso was parsing to the point of failure. To make the offsets exact, the replacements of autolinks and$$blocks that precede parsing now preserve the byte length of the text instead of substitutingURLandLaTeX.🤖 Prepared with Claude Code