fix lambda docs #162
Merged
fix lambda docs #162
Conversation
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
The lambda backslashes didn't show up in the docs because the weren't escaped for haddock.
Collaborator
|
Thanks @meipp. Can you rebase your branch against current upstream master and force push? CI is failing. EDIT: Apparently I can close and reopen to trigger the new CI actions, so never mind. |
Collaborator
|
Thanks @meipp! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The docs in Control.Monad.Accum and Control.Monad.Cont.Class lack escaping backslashes for lambdas in the haddock comments.