<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/coverage/while.cov-map, branch 1.85.1</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.85.1</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.85.1'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2024-10-11T10:04:37+00:00</updated>
<entry>
<title>coverage: Include the highest counter ID seen in `.cov-map` dumps</title>
<updated>2024-10-11T10:04:37+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2024-10-08T02:13:05+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=599f95ecc26fb68cccbf79780dd1825a4cf73eb0'/>
<id>urn:sha1:599f95ecc26fb68cccbf79780dd1825a4cf73eb0</id>
<content type='text'>
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.)
</content>
</entry>
<entry>
<title>coverage: Simplify counter expressions using simple algebra</title>
<updated>2024-05-14T03:58:40+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2024-05-14T03:51:24+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=d01df6f9aadf58a00357bd89b8fc25a44822ba77'/>
<id>urn:sha1:d01df6f9aadf58a00357bd89b8fc25a44822ba77</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>coverage: Tweak individual tests to be unaffected by `rustfmt`</title>
<updated>2024-01-16T05:14:27+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2024-01-16T03:12:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=1f9353ae2ca81b0a508e38751b0d3ab213526f56'/>
<id>urn:sha1:1f9353ae2ca81b0a508e38751b0d3ab213526f56</id>
<content type='text'>
Some of these tests use non-standard formatting that we can simulate by
strategically adding `//` line comments.

One contains `where` clauses that would be split across multiple lines, which
we can keep on one line by moving the bounds to the generic type instead.
</content>
</entry>
<entry>
<title>coverage: Migrate `tests/coverage-map` into `tests/coverage`</title>
<updated>2023-11-07T00:15:19+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2023-11-01T10:28:53+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=49127c64d6998526d9f723a653312d0cf5310454'/>
<id>urn:sha1:49127c64d6998526d9f723a653312d0cf5310454</id>
<content type='text'>
</content>
</entry>
</feed>
