Added item "Semicolons can't replace newlines" #470
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
Not sure what the best location for this is. It's minor, so I put it near the end. It's about the language, so I put it before the item concerning documentation comments. (I tried to use semicolons for newlines and found it didn't work, and went looking for confirmation that there was no way to do this. Was told in discord that it's not an option.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 adds a note that in Purescript required newlines can't be replaced by semicolons. That is, in Haskell, an expression such as a
doblock that normally uses multiple lines can be written on one line, using semicolons. This isn't possible in Purescript.Not sure what the best location for this is. It's minor, so I put it near the end. It's about the language, so I put it before the item concerning documentation comments. (I tried to use semicolons for newlines and found it didn't work, and went looking for confirmation that there was no way to do this. Was told in discord that it's not an option. So I thought I'd add the info here.)