Conversation
|
r? @aidanhs (rust_highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
|
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 |
|
Hmm, I could fix the few |
|
☔ The latest upstream changes (presumably #62192) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Hi @cuviper - ping from Triage. Please post an update here at your earliest convenience. |
|
I had further problems getting the documentation links to work out. A different approach might be to keep std-only primitive docs, and just add some kind marker indicating which methods are provided by |
This adds basic primitive documentation to
libcore. At the top level these just refer tostd, so we aren't duplicating that text, but the greater value comes from thecore-specific list of methods and trait implementations. For example,f64has far fewer methods incore, but there previously wasn't any way to know which of its methods requirestd.This also has the advantage that
coredocs will now get automatic links for the primitives in parameter lists and such, just like thestddocs do. The second commit in this pull request also updates manual links to becore/stdagnostic as much as possible.