rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2024-02-22	[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives	许杰友 Jieyou Xu (Joe)	-2/+2

2024-01-21	Rollup merge of #120015 - Zalathar:format, r=dtolnay	Nadrieril	-0/+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-17	Remove 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.
2024-01-16	coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting	Zalathar	-0/+2
	These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2023-12-15	coverage: Use `Waker::noop` in async tests	Zalathar	-26/+17

2023-11-07	coverage: Migrate `tests/run-coverage` into `tests/coverage`	Zalathar	-0/+139