Documents should clarify about arrays #17148
Comments
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this issue
Sep 10, 2014
bors
added a commit
that referenced
this issue
Sep 11, 2014
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
May 19, 2024
fix: Tracing span names should match function names When viewing traces, it's slightly confusing when the span name doesn't match the function name. Ensure the names are consistent. (It might be worth moving most of these to use `#[tracing::instrument]` so the name can never go stale. `@davidbarsky` suggested that is marginally slower, so I've just done the simple change here.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7.2.8 Vector expressions of the language reference refers to the "vector expression" and 7.2.21 Match expressions refers to the "vector pattern". However 8.1.4 Vector, Array, and Slice types of the language reference and the Rust guide refer to the same thing (at least the former) as an "array". It's odd that a "vector expression" creates an "array" rather than a "vector".
There are also dangling
<a href="#vector-types">in the language reference.Neither the language reference nor the API reference explains which traits an array implements nor what methods are available for it.
The text was updated successfully, but these errors were encountered: