Stop using higher-order macros to declare arenas#159955
Open
Zalathar wants to merge 3 commits into
Open
Conversation
This is a little more verbose than using a `[decode]` modifier, but will allow us to stop using higher-order macros when declaring arenas.
Collaborator
|
r? @camelid rustbot has assigned @camelid. Use Why was this reviewer chosen?The reviewer was selected based on:
|
Member
Author
|
This will have textual conflicts with #159893. |
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.
The arenas used by
rustc_hirandrustc_middleare declared via macros. But instead of invokingrustc_arena::declare_arena!directly, those crates declare a higher-order macro containing a list of types, and then invoke that macro withdeclare_arena!as an argument.From what I can tell, the only reason for this arrangement is so that the list of types can also contain
[decode]modifiers that produce a corresponding implementation ofRefDecodablethat decodes into the arena. But the number of types involved is small enough that it's easy to list them separately, and the advantage of doing so is that we can remove a layer of macro indirection, making it easier to navigate to the real code.There should be no change to compiler behaviour.