In rust-mode, allow typing match branches (=>) in strict mode #789
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
Rust does match branches with the fat arrow (=>). This change ensures that inserting the '>' after a '=' does not trigger a rebalancing (which would remove the '>' and be really frustrating)
|
Awesome! Even with tests ❤️ Thanks! |
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'm writing a bunch of rust lately, and have run into a problem where I couldn't insert
=>in strict mode. Soooo, this pull request adds a test & adjusts the pair logic to correctly work when=>is inserted in rust.Hope this is acceptable - it looks like all rust tests are passing with this change (: