Update a couple missed cases to the new linear arrow syntax #352
Conversation
This file contains 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
|
@aspiwack can you have a look at merge if good? |
nomeata
added
the
Non-proposal
aspiwack
approved these changes
Jul 29, 2020
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.
I believe a couple arrows were missed when changing the linear arrow syntax. (Of course, I may be mistaken – I might have missed something myself, since there was tons of discussion and I didn't read it all.)
The syntax of linear arrows underwent a couple of revisions over the course of the proposal, and I think updating these few cases was probably overlooked by accident.
The syntax section specifies the current accepted syntax as
#->and# p ->. For reference, here's the comment changing:p->to#p->and the comment changing->.to#->.