Added U+00A7, SECTION SYMBOL (for (<$>) or fmap)#11
Open
betaveros wants to merge 2 commits intoroelvandijk:masterfrom
Open
Added U+00A7, SECTION SYMBOL (for (<$>) or fmap)#11betaveros wants to merge 2 commits intoroelvandijk:masterfrom
betaveros wants to merge 2 commits intoroelvandijk:masterfrom
Conversation
sorry, Unicode U+ literals should probably be padded to four digits
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
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.
Rationale:
(<$>)orfmapis easily a more fundamental Haskell operator than many of the operators that have already been provided. So it deserves its own Unicode character.My only concern is that, given the character's commonness, some package on Hackage somewhere might use the symbol to mean something completely different and perhaps more meaningful. (I know e.g. hmatrix uses U+00BF INVERTED QUESTION MARK, U+00A6 BROKEN BAR, and U+2014 EM DASH.) But I haven't found a way to look for packages that use particular Unicode characters as operators, and I think the risk is low enough.
Also, I didn't know what to do for the copyright in the new file so I selfishly claimed all 37 lines of it for myself. You can change that if you want. (The other files' copyright years ought to be updated too.)