Skip to content
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

Confusing rustdoc layout for const functions that are unstable even in non-const contexts #125511

Closed
dead-claudia opened this issue May 24, 2024 · 2 comments · Fixed by #125599
Closed
Assignees
Labels
C-bug Category: This is a bug. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@dead-claudia
Copy link

dead-claudia commented May 24, 2024

Here's what I found:
image

What I would've expected is something closer to this (an unstable non-const function):
image

For reference, functions stable in non-const contexts but unstable in const contexts look like this:
image

@dead-claudia dead-claudia added the C-bug Category: This is a bug. label May 24, 2024
@rustbot rustbot added the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label May 24, 2024
@Rua
Copy link
Contributor

Rua commented May 24, 2024

If the whole function is unstable, then there's no point in listing the constness as unstable, and confusing if it's given as pub fn when it's actually always const. It should just show it as pub const fn?

@camelid
Copy link
Member

camelid commented May 25, 2024

@rustbot claim

@camelid camelid added the T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. label May 27, 2024
@bors bors closed this as completed in f00b02e May 27, 2024
@saethlin saethlin removed the needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants