Fix incorrect numbering in Control.Monad.Cont#180
Merged
L0neGamer merged 1 commit intohaskell:masterfrom Apr 9, 2026
Merged
Conversation
This fixes haskell#177: Incorrect numbering for Hackage docs The implicit numbering was broken so we switched to explicit enumeration. We switched to 1., 2., 3. numbering over (1), (2), (3) numbering to stay consistent accross the code base.
Collaborator
|
Could you show a picture of the new documentation? And have you checked for similar issues elsewhere? |
mniip
approved these changes
Apr 9, 2026
Contributor
Author
|
Contributor
Author
This has been the only instance in the code base of an enumerated list where the author left it up to haddock to do the counting (i.e. they wrote, I have not checked for similar problems in other repos. |
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
3 participants
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 fixes #177 : Incorrect numbering for Hackage docs
The implicit numbering was broken so we switched to explicit enumeration. We switched to 1., 2., 3. numbering over (1), (2), (3) numbering to stay consistent accross the code base.