Destabilize VaArgSafe - #162909
Destabilize VaArgSafe#162909
VaArgSafe#162909Conversation
b90e121 to
69f7122
Compare
69f7122 to
04f2f84
Compare
04f2f84 to
d0cbd07
Compare
|
rustbot has assigned @Mark-Simulacrum. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@bors try |
Destabilize `VaArgSafe`
This comment has been minimized.
This comment has been minimized.
|
Due to time sensitivity: @bors r+ rollup=never p=1 note="Backport" |
|
beta backport approved as per libs team on Zulip. A backport PR will be authored by the release team at the end of the current development cycle. Backport labels are handled by them. |
d0cbd07 to
5e3ad00
Compare
|
This pull request was unapproved. |
|
We're waiting in the queue on clippy subtree update for a few hours anyway ^^ |
|
@bors try |
This comment has been minimized.
This comment has been minimized.
Destabilize `VaArgSafe`
|
@bors r+ rollup=never p=1 note="Backport" |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 330d317 (parent) -> ed30c2c (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard ed30c2ce5e06cc4b9ab31f9a3dd20635987a8d7a --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
View all comments
Destabilizes
VaArgSafebefore 1.99 hits stable, due to open concerns about whether references should implement the trait, which would be breaking to add later.See discussion on Zulip.
Tracking issue: #162911