Add special highlighting captures for turbofishies #60
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
I didn't cherry-pick the change from attribute to function.macro because although I am already highlighting function.macros and attributes the same way in my own diary I think I will leave the choice to each user of the library decide how to highlight attributes; whether they are different from function macros or not.
For whatever reason the default highlighter picks up multi-part scopes (like @keyword.function) by picking whichever one is in the list we pass it first, for now I am going to just reorder keyword to be before function so that it picks keyword for @keyword.function instead of function, hopefully this doesn't break anything haha...
This by coincidence also solves a weird edge case where `<Option<()>>::map` would cause an @operator selector to start and never end
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.
This by coincidence also solves a weird edge case where
<Option<()>>::mapwould cause an https://github.com/operator selector to start and never end