reference
reference copied to clipboard
rust-lang
The Rust Reference
for the stabilization of https://github.com/rust-lang/rust/issues/81391 Waiting on needing an RFC: https://github.com/rust-lang/rust/issues/81391#issuecomment-2417466063
This rewrites the inline-assembly chapter to use the agreed upon style and mdbook-spec extensions. It also more formally defines certain portions and adds several more examples.
Update attributes/codegen.md to include newly added aarch64 CPU features. rust/rust PR with the new features: https://github.com/rust-lang/rust/pull/128192 List of added features: - FEAT_CSSC - FEAT_ECV - FEAT_FAMINMAX - FEAT_FLAGM2 - FEAT_FP8...
Since 1.79, the temporaries are extended in the following example: ````rust let a = if true { ..; &temp() // used to error, but now gets lifetime extended } else...
The `derive` attribute documentation should probably list the built-in traits that are derivable. To my knowledge, the list is: - `Clone` - `Hash` - `PartialEq` - `Eq` - `PartialOrd` -...
Method resolution has two steps. We collect a list of types, then we go through that list and, for each type, look to see whether there's one or more matching...
At some point, we may want to improve the grammar for blocks. The way that `rustc` works is that a block is a sequence of statements. It's probably clearer to...
The list of "guaranteed directives" at https://github.com/rust-lang/reference/blob/dad82335e200081ea498b0fb454b9ed3343f8cd5/src/inline-assembly.md#directives-support seems unclear to me which ones are target-specific. In the sections below, there are several target-specific directives. However, looking over the current list...
The "Type coercions" section says coercion is allowed from: - Function item types to fn pointers - Non capturing closures to fn pointers This ought to describe the compatibility requirements,...
The "Path expressions" section says: - "A path used as an expression context denotes either a local variable or an item.", and - "Path expressions that resolve to local or...