crater for #156977 (inhabitednes check) - #159598
Conversation
|
Let's see if this works |
|
@craterbot run mode=check start=main#3d50c25bc66853bf0ad205529d0f305a1d841b5e end=main#4a9d5368df6450bbd2fc8dde4508c3e5d83bb19d |
|
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ask in t-infra on Zulip |
|
@craterbot run start=main#3d50c25bc66853bf0ad205529d0f305a1d841b5e end=main#4a9d5368df6450bbd2fc8dde4508c3e5d83bb19d mode=check |
|
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ask in t-infra on Zulip |
|
@craterbot run mode=check-only start=master#3d50c25bc66853bf0ad205529d0f305a1d841b5e end=master#4a9d5368df6450bbd2fc8dde4508c3e5d83bb19d |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
|
Given that we have not gotten any issue filed for this it seems like the fallout of that PR can't be entirely terrible. I don't expect there to be much fallout. Some cursed type system things may no longer work because we refuse to evaluate consts that have generics in their type, and some cursed const-eval code with UB may now yield errors where it previously did not. But it's hard to predict how much code out there relies on cursed type system tricks.^^ |
|
@theemathas has been doing triage for several cycles on the crater runs so is probably the best person to answer. |
|
I think queueing up this crater run is fine. If the crater queue situation gets any worse, I'll do a crater rollup. |
|
All right. (This one here can't really be rolled up because it has to compare fixed hashes.) |
Retroactive crater run for #156977