summary refs log tree commit diff
path: root/tests/coverage/closure_macro_async.coverage
AgeCommit message (Collapse)AuthorLines
2024-02-22[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives许杰友 Jieyou Xu (Joe)-1/+1
2024-02-05coverage: Make unexpansion of closure bodies more preciseZalathar-8/+8
This improves the coverage instrumentation of closures declared in macros, as seen in `closure_macro.rs` and `closure_macro_async.rs`.
2024-01-21Rollup merge of #120015 - Zalathar:format, r=dtolnayNadrieril-1/+2
coverage: Format all coverage tests with `rustfmt` As suggested by <https://github.com/rust-lang/rust/pull/119984#discussion_r1452856806>. Test files in `tests/` are normally ignored by `x fmt`, but sometimes those files end up being run through `rustfmt` anyway, either by `rust-analyzer` or by hand. When that happens, it's annoying to have to manually revert formatting changes that are unrelated to the actual changes being made. So it's helpful for the tests in the repository to already have standard formatting beforehand. However, there are several coverage tests that deliberately use non-standard formatting, so that line counts reveal more information about where code regions begin and end. In those cases, we can use `#[rustfmt::skip]` to prevent that code from being disturbed. ``@rustbot`` label +A-code-coverage
2024-01-18coverage: Format all remaining testsZalathar-1/+2
These tests can simply be reformatted as normal, because the resulting changes are unimportant.
2024-01-17Remove unnecessary `let`s and borrowing from `Waker::noop()` usage.Kevin Reid-2/+1
`Waker::noop()` now returns a `&'static Waker` reference, so it can be passed directly to `Context` creation with no temporary lifetime issue.
2023-12-15coverage: Use `Waker::noop` in async testsZalathar-19/+7
2023-11-07coverage: Migrate `tests/run-coverage` into `tests/coverage`Zalathar-0/+79