reference
reference copied to clipboard
rust-lang
The Rust Reference
The stabilization PR is https://github.com/rust-lang/rust/pull/87220, it's going to contain a stabilization report describing the behavior of such attributes.
Add documentation about implicit lifetime bounds that the compiler can infer for functions, trait implementations, and structs. This draws from RFC 2093 (for structs) and RFC 1214 for functions and...
The closure type page needs to be updated for the 2021 changes. See [RFC 2229](https://github.com/rust-lang/rfcs/blob/master/text/2229-capture-disjoint-fields.md) and [edition guide chapter](https://github.com/rust-lang/edition-guide/blob/master/src/rust-2021/disjoint-capture-in-closures.md). (Note: PR #1059 is already open to resolve this.)
When working cross platform, in particular when producing a dylib from Rust and then again consuming it, the current resolution of `#[link(name = "mylib"]` is somewhat confusing. - If you...
See rust-lang/rust#44493 - [ ] Document existing inferred lifetime bounds in functions and impls - [ ] Document feature. Should this be documented with the existing inferred bounds? - [...
The rest of this RFC, apart from #278. - [ ] Document feature - [ ] Make use of feature where appropriate
Updates documentation to reflect the **still unstable** `arbitrary_enum_discriminant`feature (tracking issue: rust-lang/rust#60553).
This expands on several sections to specify exactly which names are introduced by items. This also contains a few tangential updates, such as explaining what `Self` is and how it...
Every item should declare what paths it adds. We can say that the canonical path for an item is its *path prefix* followed by `::` followed by the item's *path...
The Attributes section uses "macro attributes" but links to a section calling them "attribute macros"
