diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2022-08-26 14:08:44 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-26 14:08:44 +0200 |
| commit | ae838f76455461031119c9c6f33b0791c33c4fee (patch) | |
| tree | aaba5320627defd4127b9333146fb8ffc2e8c163 /compiler/rustc_mir_transform/src/coverage/mod.rs | |
| parent | e3148dc7c48e1c96b05c85f57394308a6e46c1ed (diff) | |
| parent | fab36d1713504824be4eefdd7614cf9e79ca7358 (diff) | |
| download | rust-ae838f76455461031119c9c6f33b0791c33c4fee.tar.gz rust-ae838f76455461031119c9c6f33b0791c33c4fee.zip | |
Rollup merge of #99742 - sigaloid:master, r=thomcc
Add comments about stdout locking This is the source of some confusion regarding the `println!` macro: * https://llogiq.github.io/2017/06/01/perf-pitfalls.html#unbuffered-io * https://news.ycombinator.com/item?id=18794930 * https://reddit.com/r/rust/comments/5puyx2/why_is_println_so_slow/dcua5g5/ * https://reddit.com/r/rust/comments/ab7hsi/comparing_pythagorean_triples_in_c_d_and_rust/ecy7ql8/ In some of these cases it's not the locking behavior where the bottleneck lies, but it's still mentioned as a surprise when, eg, benchmarking a million `println!`'s in a very tight loop. If there's any stylistic problems please feel free to correct me! This is my first contribution and I want to get it right :crab:
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/mod.rs')
0 files changed, 0 insertions, 0 deletions