-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
process nested obligations in autoderef #54252
Conversation
IIUC, a fix isn't needed because the original code can be switched to use |
I agree that this makes the bug workaroundable and therefore less urgent. However, this is still a bug that should be fixed.. |
c7f7cf7
to
65b44db
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At first read, seems reasonable (for what it is). Should we check perf? It feels like these are some common operations.
@bors try |
process nested obligations in autoderef This is a hack-fix to #53843, but I am worried it might break things because it makes the "inference pollution" problem worse. I need to do the "autoderef querification" thing somehow to solve t. Fixes #53843 (but introduces a bug that someone might notice). r? @nikomatsakis
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Sure, a perf run would be nice. I would not bother with figuring out the best caching strategy if it is pointless. |
Try build failure looks quite spurious to my eyes |
Yeah, the try build failure does look spurious. I'm not sure how to rerun. @bors try- |
@bors try |
2f4f9ed
to
6e93cf3
Compare
Are all these submodule changes intended? |
No. |
5d621ac
to
88f7e57
Compare
@bors try |
process nested obligations in autoderef This is a hack-fix to #53843, but I am worried it might break things because it makes the "inference pollution" problem worse. I need to do the "autoderef querification" thing somehow to solve t. Fixes #53843 (but introduces a bug that someone might notice). r? @nikomatsakis
☀️ Test successful - status-travis |
@rust-timer build 0b9d15f |
Success: Queued 0b9d15f with parent 2287a7a, comparison URL. |
⌛ Trying commit 0152d33 with merge 52335ac987cf385dd4b2f6926b273fd6462c0ade... |
@bors try- |
@bors try |
⌛ Trying commit b4db387 with merge 0b8c5828f68d7b2840b81fa51239346dc97fef5a... |
☀️ Test successful - status-travis |
@craterbot run start=master#96d1334e567237b1507cd277938e7ae2de75ff51 end=try#0b8c5828f68d7b2840b81fa51239346dc97fef5a mode=check-only |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
Yay! |
@bors r+ |
📌 Commit b4db387 has been approved by |
process nested obligations in autoderef Fixes #53843. r? @nikomatsakis
☀️ Test successful - status-appveyor, status-travis |
Avoid committing to autoderef in object method probing This fixes the "leak" introduced in #57835 (see test for details, also apparently #54252 had no tests for the "leaks" that were fixed in it, so go ahead and add one). Maybe beta-nominating because regression, but I'm against landing things on beta we don't have to. r? @nikomatsakis
Fixes #53843.
r? @nikomatsakis