-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
rustdoc: Cleanup ABI rendering #33151
Conversation
Use a common method for rendering `extern "<abi>"`. This now consistently shows `extern "C" fn` rather than just `extern fn`.
(rust_highfive has picked a reviewer for you, use r? to override) |
I personally prefer showing |
rustfmt adds |
I agree that the two should be consistent, but I would personally consider rustfmt as the one that should change in this regard. |
cc @rust-lang/tools |
It was discussed here: rust-lang/rustfmt#451. |
Looks like rustfmt changed to elide |
Seems like the default for |
I've been meaning to canvas opinions on what rustfmt should do here. I don't have a strong opinion. |
I used to put it in, but lately have switched to taking it out. I don't feel super strongly but would lean towards not including it. On Apr 23, 2016, 12:21 +0300, Nick Cameronnotifications@github.com, wrote:
|
So, what is the conclusion here? That we're not going to merge this? |
I can change this to hide the The point of this patch was consistency as rustdoc currently uses both styles in different places. For example https://doc.rust-lang.org/1.8.0/libc/fn.atexit.html has both on the same line. |
Ah, right, sorry. Consistency is certainly good. On Apr 26, 2016, 11:32 -0400, Oliver Middletonnotifications@github.com, wrote:
|
Yeah I'd be fine with just removing the rendering of |
I've removed the |
rustdoc: Cleanup ABI rendering Use a common method for rendering `extern "<abi>"`. This now consistently shows `extern fn` rather than `extern "C" fn`.
Use a common method for rendering
extern "<abi>"
.This now consistently shows
extern fn
rather thanextern "C" fn
.