fix: correct markdown header processing - #539
Merged
Merged
Conversation
Collaborator
Author
|
I added some incidental comments to some Verso code as well based on my current understanding of it, let me know if I said anything wrong. |
jcreedcmu
added a commit
to jcreedcmu/reference-manual
that referenced
this pull request
Sep 29, 2025
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Collaborator
|
Apart from nitpicky docstring stuff, I think this is a nice simplification and I think the docs were all correct. Did you have |
Collaborator
|
(or, alternatively, make sure to enable it) |
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
Co-authored-by: David Thrane Christiansen <david@davidchristiansen.dk>
jcreedcmu
added a commit
to jcreedcmu/reference-manual
that referenced
this pull request
Oct 1, 2025
jcreedcmu
added a commit
to jcreedcmu/verso
that referenced
this pull request
Oct 1, 2025
Make the type `HeaderMapping` an abbreviation instead of a definition. This change was intended as part of leanprover#539 and will make leanprover/reference-manual#599 easier to land. There's still [one place remaining](https://github.com/leanprover/reference-manual/blob/main/Manual/Meta/ErrorExplanation.lean#L639-L640) in `Manual/Meta/ErrorExplanation.lean` where it's relying on the implementation of this type, which breaks if typeclass resolution doesn't see the `ForIn` instance on `List`. Of course, we could also expose `ForIn` on `HeaderMapping`, or expose a "close all sections for this `HeaderMapping` but I'd rather decouple that decision from [the present PR](leanprover/reference-manual#599).
jcreedcmu
added a commit
that referenced
this pull request
Oct 1, 2025
Make the type `HeaderMapping` an abbreviation instead of a definition. This change was intended as part of #539 and will make leanprover/reference-manual#599 easier to land. There's still [one place remaining](https://github.com/leanprover/reference-manual/blob/main/Manual/Meta/ErrorExplanation.lean#L639-L640) in `Manual/Meta/ErrorExplanation.lean` where it's relying on the implementation of this type, which breaks if typeclass resolution doesn't see the `ForIn` instance on `List`. Of course, we could also expose `ForIn` on `HeaderMapping`, or expose a "close all sections for this `HeaderMapping` but I'd rather decouple that decision from [the present PR](leanprover/reference-manual#599).
jcreedcmu
added a commit
to jcreedcmu/verso
that referenced
this pull request
Oct 1, 2025
Previously, parts generated by `addPartFromMarkdown` were at wrong nesting depth for nontrivial structures. Error explanations (for which this code was originally written) did not exercise this but because they have fairly simple structure, without many children of the same header, or decreases of header depth. This PR simplifies the verso-nesting-depth-to-markdown-nesting-depth state, to a list of `Nat` rather than a list of pair of `Nat`s. I think without sacrificing correctness.
jcreedcmu
added a commit
to jcreedcmu/verso
that referenced
this pull request
Oct 1, 2025
Make the type `HeaderMapping` an abbreviation instead of a definition. This change was intended as part of leanprover#539 and will make leanprover/reference-manual#599 easier to land. There's still [one place remaining](https://github.com/leanprover/reference-manual/blob/main/Manual/Meta/ErrorExplanation.lean#L639-L640) in `Manual/Meta/ErrorExplanation.lean` where it's relying on the implementation of this type, which breaks if typeclass resolution doesn't see the `ForIn` instance on `List`. Of course, we could also expose `ForIn` on `HeaderMapping`, or expose a "close all sections for this `HeaderMapping` but I'd rather decouple that decision from [the present PR](leanprover/reference-manual#599).
Collaborator
Author
|
Verso docstrings were later enabled in #547 |
jcreedcmu
added a commit
to jcreedcmu/reference-manual
that referenced
this pull request
Oct 8, 2025
jcreedcmu
added a commit
to jcreedcmu/reference-manual
that referenced
this pull request
Oct 8, 2025
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.
Previously, parts generated by
addPartFromMarkdownwere at wrong nesting depth for nontrivial structures. Error explanations (for which this code was originally written) did not exercise this but because they have fairly simple structure, without many children of the same header, or decreases of header depth.This PR simplifies the verso-nesting-depth-to-markdown-nesting-depth state, to a list of
Natrather than a list of pair ofNats. I think without sacrificing correctness.