-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression: X does not live long enough #100544
Comments
I think these are two separate (unrelated) issues. #98835 had a crater run where these regressions were identified: #98835 (comment) #99413 had a crater run where there were quite a lot of regressions, but nobody has reviewed it: #99413 (comment) There are quite a few regressions in #99413, but I suspect that will need to be accepted since it is a soundness fix. |
From #98835 (comment):
I wish this had been flagged as a potential diagnostic issue back when this was identified. Filed #100572. |
In theory, we could back out of #98835, maybe with a future compat warning. |
json2rss is also #99413 FGS regresses at the same nightly as #98835, as does wonnx ft-cli is most definitely #99413 (the @rustbot label -E-needs-bisection @aliemjay provided a minimal example of the #98835-regression in their PRs: async fn test<'a>() { // `'a`, being a lifetime parameter, must be longer than the entire function body
let f = |_: &'a str| {}; // the argument is required to outlive `'a`
f(&String::new()); // an argument of shorter lifetime is passed!
} For the #99413-regressions, we don’t need a mcve, since breakage was expected from the soundness fix. @rustbot label -E-needs-mcve |
Is this actually a regression? I saw it mentioned that this is a correctness fixed introduced as a part of #98835. I think this issue is probably safe to close. |
@seanpianka I think at this point I agree with your opinion (also by looking at this comment). @jackh726 do you agree this can be closed without further action? is it a case of intended behaviour but perhaps poorly communicated to users? other interesting points to note here? thanks! |
Picked up in crater:
Slightly different error (dropped while borrowed), probably same root cause but should confirm:
The text was updated successfully, but these errors were encountered: