-
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
assume MIR types are fully normalized in ascribe_user_type #107197
Conversation
r? @wesleywiser (rustbot has picked a reviewer for you, use r? to override) |
r? types |
@bors r+ rollup=never |
(Not rolling up for bisectability, given how easy it is for normalization things to mess things up) |
⌛ Testing commit 9346eb6 with merge 2ef759353a028da14550ee904a2ce19db58edb81... |
💔 Test failed - checks-actions |
@bors retry seems spurious |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (001a77f): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
This FIXME was introduced in c6a17bf but it should've been restricted to
ascribe_user_type_skip_wf
.