| Age | Commit message (Collapse) | Author | Lines |
|
- Make links relative.
- Adjust links from old 2018-edition book.
- Fix broken link in `let` docs.
|
|
|
|
|
|
|
|
Resolves #55416
|
|
|
|
|
|
`const fn` is no longer coming soon (const keyword docs)
The `const` keyword [documentation](https://doc.rust-lang.org/std/keyword.const.html) mentions that `const fn`s are coming soon, but they have already been added.
|
|
|
|
Fixes https://github.com/rust-lang/rust/issues/57104.
|
|
|
|
|
|
|
|
|
|
This was added in the fortnight this PR spent stale. I'm hoping this
one-liner fixes it.
|
|
Dangit. I really thought I got them all.
|
|
Thanks to @Centril for these.
|
|
Most of these will eventually be filled, but right now travis-ci enjoys
complaining about the fact that there's links that lead nowhere, so
they're gone. Hopefully someone remembers to re-add them later.
|
|
|
|
It didn't strictly need to be reworked and I'm not sure my version is
better, but oh well, I'm doing it for consistency.
|
|
This commit also splits out linky-line-thingies into two lines, which
judging from the source code for tidy, should be enough to make it shut
up and accept me for who I am, dammit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I think it might be used in some other things, but I'm not fluent enough
at sifting through the rust compiler's source code to find every use of
a specific keyword.
This leaves the question of how to document the `extern` keyword, what
with how much overlap it has with `crate`, but that's used with ABI
stuff so that should be fine.
|
|
Mostly addressing notes on ambiguous syntax and spurious newlines.
|
|
Turns out writing docs on keywords that are used in multiple different
places in entirely different contexts gets a little harder. I put a
footnote on `*const` syntax just to make sure you can find it if need
be, but it might need more detail.
|
|
It's pretty basic and could do with more details, but it's a good
starter until someone else improves it.
|
|
The whole keyword docs thing is pretty new in Rust's history and needs
some work before it's a shining gem. Here's hoping I can provide that.
I basically shoved in a bunch of the most important information from the
reference and the book, along with leaving links to both at the end. I
don't think keyword docs need to have complete detail, just all the
broad strokes, so if someone's confused about a usage of a keyword they
can look at the std documentation for that keyword.
|
|
|
|
|
|
|