rust/tests/coverage, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-09-26T04:34:09+00:00Auto merge of #145882 - m-ou-se:format-args-extend-1-arg, r=petrochenkov2025-09-26T04:34:09+00:00borsbors@rust-lang.org2025-09-26T04:34:09+00:00urn:sha1:40ace17fc3891155bad26a50d60a9ab07b83bf8e
Extended temporary argument to format_args!() in all cases
Fixes https://github.com/rust-lang/rust/issues/145880 by removing the special case.
Auto merge of #143290 - azhogin:azhogin/link-pub-async-impls, r=oli-obk2025-09-01T10:54:40+00:00borsbors@rust-lang.org2025-09-01T10:54:40+00:00urn:sha1:c0bb3b98bb7aac24a37635e5d36d961e0b14f435
pub async fn impl is monomorphized when func itself is monomorphized
Implentation coroutine (`func::{closure#0}`) is monomorphized, when func itself is monomorphized.
Currently, when `pub async fn foo(..)` is exported from lib and used in several dependent crates, only 'header' function is monomorphized in the defining crate. 'header' function, returning coroutine object, is monomorphized, but the coroutine's poll function (which actually implements all the logic for the function) is not. In such situation, `func::{closure#0}` will be monomorphized in every dependency.
This PR adds monomorphization for `func::{closure#0}` (coroutine poll function), when func itself is monomorphized.
Simple test with one lib async function and ten dependent crates (executable) that use the function, shows 5-7% compilation time improvement (single-threaded).
pub async fn implementation coroutine (func::{closure#0}) is monomorphized, when func itself is monomorphized2025-09-01T06:45:00+00:00Andrew Zhoginandrew.zhogin@gmail.com2025-07-01T16:54:52+00:00urn:sha1:c2c58cbc65343f1a227885c7a5893f3e6d616e82Update tests.2025-08-26T12:46:11+00:00Mara Bosm-ou.se@m-ou.se2025-08-26T12:46:03+00:00urn:sha1:bc13565de8a16c9ba0c0da51787dc60d254c6dfacoverage: Build an "expansion tree" and use it to unexpand raw spans2025-08-24T10:29:34+00:00ZalatharZalathar@users.noreply.github.com2025-08-16T07:46:05+00:00urn:sha1:c2eb45b4a176dba37a0bce8fa9c4d46cf0d55e24coverage: Add a specific test for `#[rustfmt::skip]`2025-08-24T10:29:34+00:00ZalatharZalathar@users.noreply.github.com2025-08-17T03:41:33+00:00urn:sha1:bd8e3db94d6547829cdfd60c9dfdb6bdcdd262c3coverage: Remove all unstable support for MC/DC instrumentation2025-08-06T12:38:52+00:00ZalatharZalathar@users.noreply.github.com2025-08-06T12:02:01+00:00urn:sha1:81ed042c8cc4a1bd677c9209cf9edca6b91af04acoverage: Remove `-Zcoverage-options=no-mir-spans`2025-08-04T03:48:40+00:00ZalatharZalathar@users.noreply.github.com2025-08-02T08:20:56+00:00urn:sha1:51e62a09a376e30838db0d8ade4e3e89508357e0
This flag turned out to be less useful than anticipated, and interferes with
work towards expansion support.
coverage: Re-land "Enlarge empty spans during MIR instrumentation"2025-07-30T03:17:05+00:00ZalatharZalathar@users.noreply.github.com2025-05-04T04:09:52+00:00urn:sha1:2e6f4a59226fd82c526df0f61fefc6fea44e7750
This allows us to assume that coverage spans will only be discarded during
codegen in very unusual situations.
coverage: Treat `#[automatically_derived]` as `#[coverage(off)]`2025-07-29T09:56:31+00:00ZalatharZalathar@users.noreply.github.com2025-07-28T02:25:05+00:00urn:sha1:682f744f89e1c014e91b2fd7058c75f2056ac870