diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2015-06-09 14:59:25 -0400 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2015-06-09 14:59:25 -0400 |
| commit | f62ad7d7dfb3dc693a6119ad0791c647ec0fb498 (patch) | |
| tree | b24f8e2900db9a36c26a14d7e955a7a87d755f8f | |
| parent | 7b0f2af27f18b6c81fe6a2faab0ba96e0da3bba5 (diff) | |
remove stuff about #define
This obscures more than it helps. Fixes #25573
| -rw-r--r-- | src/doc/trpl/const-and-static.md | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/doc/trpl/const-and-static.md b/src/doc/trpl/const-and-static.md index f309dd0fad6..83461feba40 100644 --- a/src/doc/trpl/const-and-static.md +++ b/src/doc/trpl/const-and-static.md @@ -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, and using a const allows for optimizations like constant propagation not only 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. |