Skip to content

Commit

Permalink
Merge pull request #1624 from RalfJung/const-has-no-addr
Browse files Browse the repository at this point in the history
do not talk about the 'address of a constant'
  • Loading branch information
traviscross authored Sep 22, 2024
2 parents beb22c7 + cb74f78 commit 24fb268
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions src/items/constant-items.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,13 +14,12 @@ guaranteed to refer to the same memory address.
The constant declaration defines the constant value in the [value namespace] of the module or block where it is located.

Constants must be explicitly typed. The type must have a `'static` lifetime: any
references in the initializer must have `'static` lifetimes.
references in the initializer must have `'static` lifetimes. References
in the type of a constant default to `'static` lifetime; see [static lifetime
elision].

Constants may refer to the address of other constants, in which case the
address will have elided lifetimes where applicable, otherwise -- in most cases
-- defaulting to the `static` lifetime. (See [static lifetime
elision].) The compiler is, however, still at liberty to translate the constant
many times, so the address referred to may not be stable.
A reference to a constant will have `'static` lifetime if the constant value is eligible for
[promotion]; otherwise, a temporary will be created.

```rust
const BIT1: u32 = 1 << 0;
Expand Down Expand Up @@ -118,3 +117,4 @@ fn unused_generic_function<T>() {
[_Expression_]: ../expressions.md
[`Copy`]: ../special-types-and-traits.md#copy
[value namespace]: ../names/namespaces.md
[promotion]: ../destructors.md#constant-promotion

0 comments on commit 24fb268

Please sign in to comment.