Update Vim highlighting #8951
Closed
Update Vim highlighting #8951
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
- Remove highlighting of ``L"..."`` (obsolete syntax) - Remove backslash at end of line being a line continuation always (obsolete syntax; this only affects comments, actually) - Add highlighting for backslash at end of line and leading whitespace on the following line inside a string (a genuine line continuation)
I added a few and removed a few and corrected a couple, all with reference to the prelude. It ends up a slightly arbitrary decision precisely what ends up in and what doesn't, unfortunately.
This is a rather more extensive change than the last, but *ever* so much easier to maintain reasonably, as there's then something to track directly.
| syn keyword rustTrait CloneableTuple10 CloneableTuple11 CloneableTuple12 | ||
| syn keyword rustTrait ImmutableTuple2 ImmutableTuple3 ImmutableTuple4 ImmutableTuple5 | ||
| syn keyword rustTrait ImmutableTuple6 ImmutableTuple7 ImmutableTuple8 ImmutableTuple9 | ||
| syn keyword rustTrait ImmutableTuple10 ImmutableTuple11 ImmutableTuple12 |
There was a problem hiding this comment.
You can probably omit these, I don't think anyone's going to be typing these much
There was a problem hiding this comment.
@alexcrichton I figure parity is the easy way to maintain it. It also makes a distinction between things that are implicit and things that must be manually imported.
bors
added a commit
that referenced
this pull request
Sep 4, 2013
…excrichton Several changes with appropriate commit messages to explain them. The final two commits, highlighting everything in the prelude, may be a little controversial. I think it's the sensible way forward with it.
flip1995
pushed a commit
to flip1995/rust
that referenced
this pull request
Jun 16, 2022
…r=giraffate Some refactoring in `needless_late_init` changelog: none
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.
Several changes with appropriate commit messages to explain them.
The final two commits, highlighting everything in the prelude, may be a little controversial. I think it's the sensible way forward with it.