diff options
| author | Rich Kadel <richkadel@google.com> | 2021-05-03 11:23:40 -0700 |
|---|---|---|
| committer | Rich Kadel <richkadel@google.com> | 2021-05-06 12:44:49 -0700 |
| commit | cd3a8c1b7f66f4f9109ba35534c8c7ae3a325dfd (patch) | |
| tree | 60c3447d364152ac18ed55c352c2f2e043a929b2 /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 716394d6581b60c75cfdd88b8e5b876f2db88b62 (diff) | |
| download | rust-cd3a8c1b7f66f4f9109ba35534c8c7ae3a325dfd.tar.gz rust-cd3a8c1b7f66f4f9109ba35534c8c7ae3a325dfd.zip | |
Removes unneeded check of `#[no_coverage]` in mapgen
And adds tests to validate it still works. 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.
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions