From ef2bf0ca0f3b5972a875c33f8f800e0f09f6f5f5 Mon Sep 17 00:00:00 2001 From: Pen Tree Date: Mon, 21 Jan 2019 21:12:59 +0800 Subject: [PATCH] fix unreachable link seems rustc-guide already move to https://rust-lang.github.io/rustc-guide/ --- blog/content/second-edition/posts/03-vga-text-buffer/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/second-edition/posts/03-vga-text-buffer/index.md b/blog/content/second-edition/posts/03-vga-text-buffer/index.md index 7c858963..f94281a6 100644 --- a/blog/content/second-edition/posts/03-vga-text-buffer/index.md +++ b/blog/content/second-edition/posts/03-vga-text-buffer/index.md @@ -451,7 +451,7 @@ error[E0017]: references in statics may only refer to immutable values To understand what's happening here, we need to know that statics are initialized at compile time, in contrast to normal variables that are initialized at run time. The component of the Rust compiler that evaluates such initialization expressions is called the “[const evaluator]”. Its functionality is still limited, but there is ongoing work to expand it, for example in the “[Allow panicking in constants]” RFC. -[const evaluator]: https://rust-lang-nursery.github.io/rustc-guide/const-eval.html +[const evaluator]: https://rust-lang.github.io/rustc-guide/const-eval.html [Allow panicking in constants]: https://github.com/rust-lang/rfcs/pull/2345 The issue about `ColorCode::new` would be solvable by using [`const` functions], but the fundamental problem here is that Rust's const evaluator is not able to convert raw pointers to references at compile time. Maybe it will work someday, but until then, we have to find another solution.