Repository navigation
regression: cannot move out of shared reference #109744
Description
Activity
I think it's indeed because the packed hard error and derive on packed structs changes both landed in 1.69.
twain-0.1.0,icu_locale_canonicalizer-0.6.0, ormars-research.binunpack-rs, all bisect to the latter, but the fact that they compiled on crater since 1.62 is likely because the deny-by-default lint was capped.Yep, sounds right. #104429 (comment) is the comment with explanation of the changes in derive on packed structs.
Removing prioritization, this seems like something we can just mention in relnotes as expected breakage.
Triage: Not sure if this was mentioned in the release notes.
If it was not mentioned, it seems weird to do now.
If it was mentioned, there is no further action to take as far as I can tell.
Closing.
I suspect these may relate to the packed hard error, but it's not very clear what has changed here. Maybe a bisection will help. (I seem to recall a change in derive desugaring, maybe this is caused by that? It did have known regressions at the time, IIRC, though this seems like more than I recall).