rust/tests/coverage/unicode.coverage, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-05-06T10:42:25+00:00coverage: Only merge adjacent coverage spans2025-05-06T10:42:25+00:00ZalatharZalathar@users.noreply.github.com2025-04-12T07:52:55+00:00urn:sha1:4d5a1acebfe031ca2af75786295a2cd2a0633943
This also removes some manipulation of the function signature span that only
made sense in the context of merging non-adjacent spans.
coverage: Shrink call spans to just the function name2025-04-01T02:07:33+00:00ZalatharZalathar@users.noreply.github.com2025-03-29T10:33:01+00:00urn:sha1:577272eedeaace00aa695135b3b8fee3768536a5
This is a way to shrink call spans that doesn't involve mixing different spans,
and avoids overlap with argument spans.
This patch also removes some low-value comments that were causing rustfmt to
ignore the match arms.
coverage: Restrict empty-span expansion to only cover `{` and `}`2024-11-08T09:43:08+00:00ZalatharZalathar@users.noreply.github.com2024-11-05T10:59:10+00:00urn:sha1:3c30fe3423b1e7d92584436493bd8fa6f17e13d0[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives2024-02-22T16:04:04+00:00许杰友 Jieyou Xu (Joe)jieyouxu@outlook.com2024-02-22T12:10:29+00:00urn:sha1:6e48b96692d63a79a14563f27fe5185f122434f8coverage: Discard spans that fill the entire function body2024-02-15T23:57:03+00:00ZalatharZalathar@users.noreply.github.com2024-02-15T07:12:27+00:00urn:sha1:cd9021e8cb1ab6cf5bdf341d7e0538703d86fc5b
When we try to extract coverage-relevant spans from MIR, sometimes we see MIR
statements/terminators whose spans cover the entire function body. Those spans
tend to be unhelpful for coverage purposes, because they often represent
compiler-inserted code, e.g. the implicit return value of `()`.
coverage: `llvm-cov` expects column numbers to be bytes, not code points2024-01-08T10:58:46+00:00ZalatharZalathar@users.noreply.github.com2023-12-15T03:12:46+00:00urn:sha1:6971e9332d9a7fb1567a6df0f30d03452f505ed3