nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-30 02:33:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rollup merge of #26133 - steveklabnik:gh25573, r=alexcrichton

Browse Source 
This obscures more than it helps.

Fixes #25573
This commit is contained in:
Steve Klabnik 2015-06-09 17:24:44 -04:00
commit 496fe4d51a
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/doc/trpl/const-and-static.md
View File

@ -78,7 +78,3 @@ Almost always, if you can choose between the two, choose `const`. It’s pretty
rare that you actually want a memory location associated with your constant, rare that you actually want a memory location associated with your constant,
and using a const allows for optimizations like constant propagation not only and using a const allows for optimizations like constant propagation not only
in your crate but downstream crates. in your crate but downstream crates.
A const can be thought of as a `#define` in C: it has metadata overhead but it
has no runtime overhead. “Should I use a #define or a static in C,” is largely
the same question as whether you should use a const or a static in Rust.