syntax: allow stmt/expr macro invocations to be delimited by []. #12947
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
this is useful for macros like vec! which construct containers
|
I think this would be neat. |
|
Yes, theoretically this should go via the RFC process but an exception was made, and this was accepted in the meeting: https://github.com/mozilla/rust/wiki/Meeting-weekly-2014-03-25#-on-macros (Needs a rebase.) |
|
bump |
bors
added a commit
that referenced
this pull request
Apr 1, 2014
this is useful for macros like vec! which construct containers rebase of #12947 because I'm impatient.
|
should be closed, was merged in other PR |
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Aug 9, 2022
Don't switch workspace on vfs file changes from libraries When r-a starts up, it starts switching the workspace before all vfs events have been processed which causes us to switch workspace multiple times until all vfs changes have been processed. This scales with the size of the project and its dependencies. If workspace files from dependencies as well as the sysroot get loaded, we shouldn't switch the workspace as those have no impact on the project workspace.
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Aug 23, 2022
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Aug 23, 2022
Revert rust-lang#12947, trigger workspace switches on all structure changes again Closes rust-lang/rust-analyzer#13029
flip1995
pushed a commit
to flip1995/rust
that referenced
this pull request
Jun 27, 2024
…xFrednet Pause assignments to @xFrednet for summer break 🏖️ I'm only removing myself from the assignment roulette as I want to allow `r? xFrednet` for `gh-pages` and other updates. So feel free to still `r?` me. r? `@ghost` 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.
this is useful for macros like vec! which construct containers
This is a followup to @huonw's earlier change which allowed
{}to be used as delimiters. I'm acting at the behest of @eddyb on IRC, who also wantedvec![a, b, c]. Is this the sort of change which now requires going through the RFC process?