-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Use absolute paths in procedural macros #23784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alice-i-cecile
merged 6 commits into
bevyengine:main
from
DavidCrossman:proc_macro_absolute_paths
May 4, 2026
Merged
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1c26037
Use absolute paths in proc macros
DavidCrossman 6be5fdd
More absolute paths
DavidCrossman 1e5566e
Remove `FQVec`
DavidCrossman ac8d657
Merge branch 'origin/main' into proc_macro_absolute_paths
DavidCrossman 1eb2f6a
Merge branch 'main' into proc_macro_absolute_paths
DavidCrossman 93665e7
Merge remote-tracking branch 'origin/main' into proc_macro_absolute_p…
DavidCrossman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to introduce an
FQFnMuthere, similar to other FQ types used elsewhere?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what the policy should be for adding new FQ types; adding every type in
core/stdwould be excessive, so just the ones we use? I addedFQIteratorandFQIntobecause they appeared a few times (Iterator6 times,Into9 times). I could addFQFnMut, sinceFnMutappears 3 times, but I would also need to addFQFn(appears once) andFQFnOnce(doesn't appear) for parity.I'd like to keep changes to the
fq_stdmodule small in this PR, as the focus is fixing hygiene issues. I think the module could be improved (FQBoxin particular) in a later PR focused on code quality.