Fix haddock for threadDelay
#80
Merged
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
`threadDelay` calls `Control.Concurrent.threadDelay`, which takes an argument in microseconds, instead of milliseconds as the documentation specified. This commit fixes that typo.
newhoggy
approved these changes
Apr 23, 2025
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.
Context
threadDelaycallsControl.Concurrent.threadDelay, which takes an argument in microseconds, instead of milliseconds as the documentation specified. This commit fixes that typo.How to trust this PR
Have a look at the documentation for
Control.Concurrent.threadDelay, notice that the argument is treated as a number of microseconds.Additionally, one can call
H.threadDelay 10_000andH.threadDelay 10_000_000, and notice that only the second call delays the thread for 10 seconds.