reference
reference copied to clipboard
rust-lang
The Rust Reference
The rust reference states: > Most primitives are generally aligned to their size, although this is platform-specific behavior. In particular, on x86 u64 and f64 are only aligned to 32...
the `.thumb` directive is in the ARM-specific list of guaranteed directives. If `.thumb` is, then `.arm` should also be as well. Otherwise we should tell people to exclusively stick to...
Originally at https://github.com/rust-lang/rust/issues/41060 The [reference](https://doc.rust-lang.org/nightly/reference/tokens.html#integer-literals) currently says the following for integer literals > The type of an unsuffixed integer literal is determined by type inference: [...] If the program context...
I think there are some types missing from special-types-and-traits.md. In particular, I *think* `Fn`, `FnMut`, and `FnOnce` are special. What is the criteria for being special? Is there anything else...
Currently this compiles: ```rust fn foo() -> i32 { {3} } ``` According to https://doc.rust-lang.org/nightly/reference/expressions/block-expr.html , the {3} part cannot be parsed as tail expression, since it's not `ExpressionWithoutBlock`. If...
This PR updates the reference to fulfill the documentation requirement of the stabilization checklist for RFC 2972, tracked at https://github.com/rust-lang/rust/issues/90957 .
https://github.com/rust-lang/reference/pull/1194#issuecomment-1101856264 suggests documenting how `main()`s return value affects the process's exit status. I think the Reference doesn't currently have anything to say about what happens after `main()` returns. I suggest...
Macro matchers allow `$` as the last token of a token tree: ```rust macro_rules! foo { ($) => {}; (last$) => {}; ({$}) => {}; ([$]) => {}; (($)) =>...