Explain what type errors have to do with purity#65
Open
gelisam wants to merge 1 commit into
Open
Conversation
To someone who isn't yet familiar with Haskell's syntax, the string concatenation example looks like the type error is that a string is being concatenated with a function. Here is an example which better explains how using an IO computation in a pure context can lead to a type error. As a bonus, the new text no longer claims that "you cannot mix and match purity with impurity". It's not true: we can mix them, but the result must be marked as impure.
Member
|
Cool. Content sounds good from looking at the commit, I'll pull it to check the size before merging. |
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
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.
To someone who isn't yet familiar with Haskell's syntax, the string
concatenation example looks like the type error is that a string is
being concatenated with a function. Here is an example which better
explains how using an IO computation in a pure context can lead to a
type error.
As a bonus, the new text no longer claims that "you cannot mix and match
purity with impurity". It's not true: we can mix them, but the result
must be marked as impure.