-
Notifications
You must be signed in to change notification settings - Fork 13k
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
introduce type-op for user-type ascription in NLL #55323
Conversation
📌 Commit 05a9b1197860849ff95370e56c0e6c74b2f111ee has been approved by |
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 |
Lots of annoying boilerplate.
@bors r- Fails tidy. |
Add regression tests for rust-lang#55219 and rust-lang#55241 Also another test where a duplicate-like error appears to have been suppressed; I'm not 100% sure why this output changes, though I could imagine that some duplicate suppression is enabled by this PR.
05a9b11
to
62f0fc5
Compare
@bors r=pnkfelix Passes |
📌 Commit 62f0fc5 has been approved by |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 62f0fc5 has been approved by |
⌛ Testing commit 62f0fc5 with merge 39a47b87f47f5eb044778fd6c3ba77cdba5b8078... |
💥 Test timed out |
@bors retry AppVeyor got stuck and not responding. |
☀️ Test successful - status-appveyor, status-travis |
Handle user-type ascription in a type operator, which gives us a lot more flexibility around the order in which we resolve things.
r? @pnkfelix
Fixes #55219
Fixes #55241