-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Improve display of const unstable display feature info #135830
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
base: master
Are you sure you want to change the base?
Improve display of const unstable display feature info #135830
Conversation
If this works with methods, can you add an example and test case for that? Or, if not, mention that it doesn't work in the PR? |
Same code for both but you're right, better ensure it. |
b77b18a
to
a6bbf15
Compare
Extended test to check on methods as well and added screenshot. |
@rfcbot poll |
Team member @notriddle has asked teams: T-rustdoc-frontend, for consensus on: |
This seems a little too similar to normal unstable API annotations to me. Skimming the docs I think I would miss the const word and just overlook the method as unstable. |
What if we showed the |
The important part here is to have the feature name accessible and copyable. |
If that's the only problem, then we can reuse the popover mechanics from Notable Traits to power the tooltip. |
Yeah, I agree. I actually didn't even notice that the unstable-info box was just about the const-instability at first. |
|
It's extra JS when we can have it inlined without. I'm definitely not a big fan. |
☔ The latest upstream changes (presumably #140695) made this pull request unmergeable. Please resolve the merge conflicts. |
Fixes #131618.
It looks like this:
And like this for methods:
You can check it online here.
r? @notriddle