Highlight Rust async and await as keywords - #3849
Draft
coyaSONG wants to merge 2 commits into
Draft
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
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.
Summary
asyncandawaituse the control-keyword scope.awaitexpression to the Rust syntax fixtureCloses #1534.
Root cause
bat's pinned Sublime Packages revision predates Rust async/await syntax, so both tokens fell through to ordinary identifier styling.
Validation
async/awaitrender with the Rust control-keyword color whileasync_fooremains a function identifiercargo fmt --checkcargo test --lockedgit diff --checkAI assistance
OpenAI Codex was used to inspect the issue and repository guidance, implement the change, and run the checks listed above.