From 3fb42cfb7c3932004a9a7295b5e19f28f0f7fff2 Mon Sep 17 00:00:00 2001 From: Mendess2526 Date: Thu, 3 Jan 2019 19:23:25 +0000 Subject: [PATCH] const fn no longer comming soon on const docs --- src/libstd/keyword_docs.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/libstd/keyword_docs.rs b/src/libstd/keyword_docs.rs index 4ca62cca94bc8..7f1509a92b4f5 100644 --- a/src/libstd/keyword_docs.rs +++ b/src/libstd/keyword_docs.rs @@ -47,8 +47,8 @@ mod as_keyword { } /// /// 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 -/// to be most things that would be reasonable to have a constant (barring `const fn`s, coming -/// soon). For example, you can't have a File as a `const`. +/// to be most things that would be reasonable to have a constant (barring `const fn`s). For +/// 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 /// all others in a Rust program. For example, if you wanted to define a constant string, it would