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

Age	Commit message (Collapse)	Author	Lines
2025-05-06	coverage: Only merge adjacent coverage spans	Zalathar	-18/+30
	This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-05-06	coverage-dump: Dump filenames instead of global file IDs (and bless)	Zalathar	-4/+4

2025-04-01	coverage: Don't split bang-macro spans, just truncate them	Zalathar	-8/+8

2025-01-16	coverage: Completely overhaul counter assignment, using node-flow graphs	Zalathar	-61/+59

2024-12-23	Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, ↵	Zalathar	-8/+8
	r=wesleywiser" This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
2024-12-16	Stabilize #[coverage] attribute	ltdk	-8/+8

2024-12-07	coverage: Prefer to visit nodes whose predecessors have been visited	Zalathar	-7/+6

2024-12-04	coverage: Add an extra "transcribe" step after counter creation	Zalathar	-24/+19

2024-10-11	coverage: Include the highest counter ID seen in `.cov-map` dumps	Zalathar	-0/+4
	When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.)
2024-05-14	coverage: Simplify counter expressions using simple algebra	Zalathar	-16/+10
	Some of these cases currently don't occur in practice, but are included for completeness, and to avoid having to add them later as branch coverage and MC/DC coverage start building more complex expressions.
2024-04-17	coverage: Move branch coverage tests into a subdirectory	Zalathar	-0/+98