-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Display tokens for fn qualifiers #58447
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
Conversation
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
cc @rust-lang/rustdoc @euclio I'm... not too keen on this? It doesn't seem worth it to specially call out " One thing that this PR changes that may be necessary to track/test is that you've changed the Display output of the "alternate" mode of the function signature type and the keyword types. This is meant to print plain-text, and is used to calculate whether to line-wrap the text of an item. Since You should also make sure to update the tests that failed on travis. |
Yep, will do, but I would like to get feedback first. If people don't want this, I don't want to spend more time on it 😛 |
I'm not a big fan either... It doesn't "fit" in whole layout. |
I wonder if we could achieve the same effect with syntax highlighting? |
One other thing is that since the names of the functions are aligned, I find them easier to glance through. |
☔ The latest upstream changes (presumably #58578) made this pull request unmergeable. Please resolve the merge conflicts. |
Since the feedback seems to be negative, I'm going to go ahead a close this. Thanks anyway :) |
My goal was to make it easier to see what qualifiers are added to a method.
What do people think? Is this an improvement?
r? @QuietMisdreavus
Sample screenshots: