Skip to content
This repository was archived by the owner on Sep 30, 2020. It is now read-only.

Commit c895374

Browse files
authored
Merge pull request #660 from nc-x/master
Fix minor nitpick in the FAQ
2 parents ca0671e + fcf7000 commit c895374

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

en-US/faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1295,8 +1295,8 @@ Converting a C-style enum to an integer can be done with an `as` expression, lik
12951295

12961296
Converting in the other direction can be done with a `match` statement, which maps different numeric values to different potential values for the enum.
12971297

1298-
<h3><a href="#why-do-rust-programs-use-more-memory-than-c" name="why-do-rust-programs-use-more-memory-than-c">
1299-
Why do Rust programs use more memory than C?
1298+
<h3><a href="#why-do-rust-programs-have-larger-binary-sizes-than-C-programs" name="why-do-rust-programs-have-larger-binary-sizes-than-C-programs">
1299+
Why do Rust programs have larger binary sizes than C programs?
13001300
</a></h3>
13011301

13021302
There are several factors that contribute to Rust programs having, by default, larger binary sizes than functionally-equivalent C programs. In general, Rust's preference is to optimize for the performance of real-world programs, not the size of small programs.

0 commit comments

Comments
 (0)