<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/coverage/await_ready.coverage, branch try-perf</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=try-perf</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=try-perf'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-05-06T10:42:25+00:00</updated>
<entry>
<title>coverage: Only merge adjacent coverage spans</title>
<updated>2025-05-06T10:42:25+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2025-04-12T07:52:55+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=4d5a1acebfe031ca2af75786295a2cd2a0633943'/>
<id>urn:sha1:4d5a1acebfe031ca2af75786295a2cd2a0633943</id>
<content type='text'>
This also removes some manipulation of the function signature span that only
made sense in the context of merging non-adjacent spans.
</content>
</entry>
<entry>
<title>Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, r=wesleywiser"</title>
<updated>2024-12-23T01:30:37+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2024-12-22T03:26:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=87c2f9a5be900e835f3c41cec2886d54ec0ca012'/>
<id>urn:sha1:87c2f9a5be900e835f3c41cec2886d54ec0ca012</id>
<content type='text'>
This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing
changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
</content>
</entry>
<entry>
<title>Stabilize #[coverage] attribute</title>
<updated>2024-12-17T02:07:06+00:00</updated>
<author>
<name>ltdk</name>
<email>usr@ltdk.xyz</email>
</author>
<published>2024-09-23T23:40:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=cb487cc2fa3c5ebfddd22d6721cf1669943c1774'/>
<id>urn:sha1:cb487cc2fa3c5ebfddd22d6721cf1669943c1774</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Stabilize noop_waker</title>
<updated>2024-12-05T22:14:17+00:00</updated>
<author>
<name>Eric Holk</name>
<email>ericholk@microsoft.com</email>
</author>
<published>2024-11-16T01:42:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=72ce1ab42f3be927f6f039a592222e054a0b0eaf'/>
<id>urn:sha1:72ce1ab42f3be927f6f039a592222e054a0b0eaf</id>
<content type='text'>
Co-authored-by: zachs18 &lt;8355914+zachs18@users.noreply.github.com&gt;
</content>
</entry>
<entry>
<title>coverage: Extract `executor::block_on` from several async coverage tests</title>
<updated>2024-09-10T06:08:36+00:00</updated>
<author>
<name>Zalathar</name>
<email>Zalathar@users.noreply.github.com</email>
</author>
<published>2024-09-06T05:41:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e96b4e479a3835d43d3c0bfd1028b5ac9d99cfec'/>
<id>urn:sha1:e96b4e479a3835d43d3c0bfd1028b5ac9d99cfec</id>
<content type='text'>
By moving `block_on` to an auxiliary crate, we avoid having to keep a separate
copy of it in every async test.

(This also incorporates some small tweaks to the headers in `await_ready.rs`.)
</content>
</entry>
<entry>
<title>coverage: Treat await similar to a macro</title>
<updated>2024-09-06T05:01:59+00:00</updated>
<author>
<name>Jonathan Conder</name>
<email>jono.conder@gmail.com</email>
</author>
<published>2024-09-05T22:25:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=25d183057edcf5d24ba0dcc8d5222a2a954aa80f'/>
<id>urn:sha1:25d183057edcf5d24ba0dcc8d5222a2a954aa80f</id>
<content type='text'>
Currently `await` is only counted towards coverage if the containing
function is suspended and resumed at least once. This is because it
expands to code which contains a branch on the discriminant of `Poll`.

By treating it like a branching macro (e.g. `assert!`), these
implementation details will be hidden from the coverage results.
</content>
</entry>
<entry>
<title>coverage: Add test to codify existing behavior</title>
<updated>2024-09-06T04:50:23+00:00</updated>
<author>
<name>Jonathan Conder</name>
<email>jono.conder@gmail.com</email>
</author>
<published>2024-09-06T00:52:32+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=3446ca535ecead268a4c8393ba7a48fd783b363a'/>
<id>urn:sha1:3446ca535ecead268a4c8393ba7a48fd783b363a</id>
<content type='text'>
Currently `await` is only counted towards coverage if the containing
function is suspended and resumed at least once. A future commit will
fix this and update the test to reflect the new behavior.
</content>
</entry>
</feed>
