-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
Use tcx.ty_error_with_guaranteed in more places, rename variants
#108369
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
Conversation
|
r? @jackh726 (rustbot has picked a reviewer for you, use r? to override) |
|
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (07c993e): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. |
ty_error_with_guaranteedmore so we don't delay so many span bugsty_error_with_guaranteedtoty_error,ty_errortoty_error_misc. This is to incentivize using the former over the latter in cases where we already are witness to aErrorGuaranteedtoken.Second commit is just name replacement, so the first commit can be reviewed on its own with more scrutiny.