diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-05-07 15:20:25 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-07 15:20:25 +0900 |
| commit | b088318985499c14630bdcf1629f3988da6432a7 (patch) | |
| tree | 5f87921d56a99f235a530004e43d174c739036fc /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 283ef8678461f8052d6ab74d0687c00b4f5c9f9d (diff) | |
| parent | cd3a8c1b7f66f4f9109ba35534c8c7ae3a325dfd (diff) | |
| download | rust-b088318985499c14630bdcf1629f3988da6432a7.tar.gz rust-b088318985499c14630bdcf1629f3988da6432a7.zip | |
Rollup merge of #84875 - richkadel:no-coverage-dont-check-unused, r=tmandry
Removes unneeded check of `#[no_coverage]` in mapgen There is an anticipated feature request to support a compiler flag that only adds coverage for specific files (or perhaps mods). As I thought about where that change would need to be supported, I realized that checking the attribute in mapgen (for unused functions) was unnecessary. The unused functions are only synthesized if they have MIR coverage, and functions with the `no_coverage` attribute will not have been instrumented with MIR coverage statements in the first place. New tests confirm this. Also, while adding tests, I updated resolved comments and FIXMEs in other tests, and expanded comments and tests on one remaining issue that is still not resolved. r? `@tmandry` cc: `@wesleywiser`
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions