-
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 in aligner-0.1.3, Rust 1.17 #40952
Comments
This affects https://github.com/GGist/bip-rs/tree/master/bip_metainfo at 2e7b786ed48422b48b2e5d4679d411dd894d5c95 as well cc @GGist |
Er sorry everyone cc'd, looks like the regression is with pbr, not other crates. |
Thanks for letting me know that @alexcrichton. fixed in pbr-1.0.0-alpha.3. |
Out of curiosity, do you know what change to rust caused this? |
I didn't dig into this, but here's the fix that solved the issue. |
Thanks @a8m, sounds like a "standard change that causes inference regressions", but I'm not personally quite ready to close this out. @rust-lang/libs any thoughts on which PR may have caused this? |
@alexcrichton I'm not sure which particular PR, but we've definitely been r+-ing a bunch of |
Actually taking a look at the code, my guess is that this is caused by #40028 which added the second Good lord that's a subtle inference issue. |
@aturon I definitely want to disable input type inference, at least for some traits, if not by default. (I think in retrospect it ought to be something one can opt into on the impl -- i.e., it's kind of a declaration that you promise not to add further impls with the same self type, similar to a negative impl declaration.) |
Ok we discussed this during libs triage the other day, and the conclusion was to close this. The known regressions have been fixed and we'd otherwise categorize this under "known breakage". If this comes up over time though please let us know as we're always interested in understanding when changes like this cause problems! |
https://github.com/kaegi/aligner
cc @kaegi
The text was updated successfully, but these errors were encountered: