-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Use named arguments for {,u}int_impls
macro
#108279
Conversation
This makes it easier to understand.
This makes it easier to understand.
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
I wonder if it makes sense to distinguish here between "used in docs" vs "not used in docs", say via a |
Hmm, I suppose there's something fundamental here: the only reason that these have to be macro parameters at all is to use them lexically in docs. Whenever they're used by actual code, they could have just been private associated types/constants instead. (For example, it could use |
But regardless, this PR is still good-to-go on its own as a nice improvement @bors r+ rollup (It's making me think that maybe |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#108241 (Fix handling of reexported macro in doc hidden items) - rust-lang#108254 (Refine error span for trait error into borrowed expression) - rust-lang#108255 (Remove old FIXMEs referring to rust-lang#19596) - rust-lang#108257 (Remove old FIXME that no longer applies) - rust-lang#108276 (small `opaque_type_origin` cleanup) - rust-lang#108279 (Use named arguments for `{,u}int_impls` macro) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This makes it way easier to understand.
r? @scottmcm