bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

const fn no longer comming soon on const docs

Browse source
This commit is contained in:
Mendess2526 2019-01-03 19:23:25 +00:00
parent 2442823ef5
commit 3fb42cfb7c
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
src/libstd/keyword_docs.rs
View file

@ -47,8 +47,8 @@ mod as_keyword { }
/// ///
/// Constants must be explicitly typed, unlike with `let` you can't ignore its type and let the /// Constants must be explicitly typed, unlike with `let` you can't ignore its type and let the
/// compiler figure it out. Any constant value can be defined in a const, which in practice happens /// compiler figure it out. Any constant value can be defined in a const, which in practice happens
/// to be most things that would be reasonable to have a constant (barring `const fn`s, coming /// to be most things that would be reasonable to have a constant (barring `const fn`s). For
/// soon). For example, you can't have a File as a `const`. /// example, you can't have a File as a `const`.
/// ///
/// The only lifetime allowed in a constant is `'static`, which is the lifetime that encompasses /// The only lifetime allowed in a constant is `'static`, which is the lifetime that encompasses
/// all others in a Rust program. For example, if you wanted to define a constant string, it would /// all others in a Rust program. For example, if you wanted to define a constant string, it would