[rustdoc] unclear experimental api notes

[liigo]

Which API is a nightly-only experimental API? The one followed by the note, or the one it follows? It's not very clear to me.

[hellow554]

You are right. Any ideas how to improve it?
One solution could be an indention on the same level as the methodcomment is.

Any other ideas?

[liigo]

How about ...

escape_debug is a nightly-only experimental API

or

🡹⇪↑⇪This is a nightly-only experimental API

[GuillaumeGomez]

The indent change seems like a better idea from my point of view so I'll go for this one.

[QuietMisdreavus]

It doesn't seem like the indentation fix is actually doing anything for the issue you're describing. You seem to have more of an issue about the unstable banner appearing outside the "folded" docs, creating a situation where it's not obvious which function declaration it's attached to, at least when everything's folded up. Would folding the unstable banner inside the docs help?

[hellow554]

You are totaly right, I didn't even noticed it! That would be good as well, but then you have to explictly unfold the item (if you folded all items, for example with the keyboard) to see, that it is unstable.
So I am a little bit indecisive. One may want to hide the unstable box, but you also should always be able to see, that that one is unstable? :| Hmmm... @GuillaumeGomez help! 😆

[liigo]

How about tag it with experimental/unstable/0.0.0 ? (and a popup tooltip)

[hellow554]

I really like the expiremental flag. 0.0.0 is not that expressive I think. Or instead of experimental nightly-only? Or use a yellow-ish background?

[GuillaumeGomez]

We can't put it on the same line, it's already super loaded.

[liigo]

We can't put it on the same line, it's already super loaded.

0.0.0 (or exp.) is not longer than 1.2.0, I think.

[GuillaumeGomez]

This isn't the issue. In case you have a super long function/trait/whatever name, it'll be very ugly and difficult to read. This line is at its max length so we'll have to find another location.