You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On 1.58, [profile.dev] opt-level=1 implies that a crate being tested with cargo test without a -C opt-level argument, but builds all dependent crates (including workspace crates, if there's a workspace dep, from what I can see) with -C opt-level=1. On 1.59 this changed to include all crates getting compiled with -C opt-level=1, increasing compile time and increasing performance (obviously).
Given its been a while, it seems like the correct solution is to simply amend the release notes to point this out.
Hm, I don't believe there were any changes to profiles in 1.59. Unfortunately, I can't reproduce what you are referring to. Can you put together a set of steps to reproduce the issue? For example:
cargo new foo
cd foo
cat >> Cargo.toml << EOF
[dependencies]
itoa = "1.0"
[profile.dev]
opt-level = 1
EOF
cargo +1.58.0 test -v
Problem
On 1.58,
[profile.dev] opt-level=1
implies that a crate being tested withcargo test
without a-C opt-level
argument, but builds all dependent crates (including workspace crates, if there's a workspace dep, from what I can see) with-C opt-level=1
. On 1.59 this changed to include all crates getting compiled with-C opt-level=1
, increasing compile time and increasing performance (obviously).Given its been a while, it seems like the correct solution is to simply amend the release notes to point this out.
CC rust-lang/rust#97460 (comment)
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
No response
The text was updated successfully, but these errors were encountered: