Use = [..] in example #76
Merged
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
dtolnay
reviewed
Dec 6, 2023
There was a problem hiding this comment.
Thanks!
Please make sure there is an issue filed upstream with CLion. This has been legal syntax in stable Rust for over 3.5 years.
Is there some setting equivalent to rust-analyzer.procMacro.enable or rust-analyzer.procMacro.attributes.enable that might avoid the codepath where the pre-expansion input is being treated as an error by the IDE?
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.
CLion likes this syntax more because it is valid before proc macro:
For the reference, this is how it looks like in CLion: