From f62ad7d7dfb3dc693a6119ad0791c647ec0fb498 Mon Sep 17 00:00:00 2001 From: Steve Klabnik Date: Tue, 9 Jun 2015 14:59:25 -0400 Subject: [PATCH] remove stuff about #define This obscures more than it helps. Fixes #25573 --- src/doc/trpl/const-and-static.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/doc/trpl/const-and-static.md b/src/doc/trpl/const-and-static.md index f309dd0fad6d9..83461feba40d2 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.