michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 22:37:49 +00:00
Code Issues Projects Releases Wiki Activity

Merge #530

Browse Source 
530: fix unreachable link r=phil-opp a=zyctree

seems rustc-guide already move to https://rust-lang.github.io/rustc-guide/

Co-authored-by: Pen Tree <appletree2479@outlook.com>
This commit is contained in:
bors[bot]
2019-01-21 13:31:37 +00:00
parent cdbcb6b981 ef2bf0ca0f
commit 19b7fbc350
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/content/second-edition/posts/03-vga-text-buffer/index.md
View File

@@ -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.