rust/compiler/rustc_trait_selection/src, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-10-03T14:32:23+00:00Don't normalize higher-ranked assumptions if they're not used2025-10-03T14:32:23+00:00Michael Gouletmichael@errs.io2025-10-03T14:32:11+00:00urn:sha1:e3f104608c0ad26e80b1ebedef2ab8a748189e52Auto merge of #147138 - jackh726:split-canonical-bound, r=lcnr2025-10-02T08:09:33+00:00borsbors@rust-lang.org2025-10-02T08:09:33+00:00urn:sha1:4b9c62b4da3e17cee99d3d2052f1c576b188e2a8
Split Bound index into Canonical and Bound
See [#t-types/trait-system-refactor > perf `async-closures/post-mono-higher-ranked-hang.rs`](https://rust-lang.zulipchat.com/#narrow/channel/364551-t-types.2Ftrait-system-refactor/topic/perf.20.60async-closures.2Fpost-mono-higher-ranked-hang.2Ers.60/with/541535613) for context
Things compile and tests pass, but not sure if this actually solves the perf issue (edit: it does). Opening up this to do a perf (and maybe crater) run.
r? lcnr
Rollup merge of #147199 - jdonszelmann:outdated-comment-infctx, r=lcnr2025-10-01T12:15:01+00:00Stuart CookZalathar@users.noreply.github.com2025-10-01T12:15:01+00:00urn:sha1:d4a0f21290ac23337ef385d539c72896c3373509
remove outdated comment in (inner) `InferCtxt`
This comment seems to have stopped being relevant around 3 years ago after https://github.com/rust-lang/rust/commit/9f95c605f83bcf4c158ea4b3fd5a7abb825a4178. A map? what map? :P
r? `@lcnr`
remove outdated context (inner) infctx2025-09-30T19:56:06+00:00Jana Dönszelmannjana@donsz.nl2025-09-30T12:01:05+00:00urn:sha1:bdebd479acb692319ace3f88bf874ea365503199Rollup merge of #147184 - jdonszelmann:bevy-outlives-bound, r=lcnr2025-09-30T19:53:35+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-09-30T19:53:35+00:00urn:sha1:598ba1f65f84e6627ba601bec669526c2f3cf128
Fix the bevy implied bounds hack for the next solver
The diff is trivial, of course, and basically what you already suggested. Mostly dug around a bunch to learn. I hope this is roughly what you had in mind.
Fixes https://github.com/rust-lang/trait-system-refactor-initiative/issues/236.
r? `@lcnr`
Rollup merge of #146617 - Jules-Bertholet:E0277-NOFORN, r=SparrowLii2025-09-30T19:53:34+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-09-30T19:53:34+00:00urn:sha1:014e0af1497aaa932fc6c51eb4b2e6f9e9fab63f
Don’t suggest foreign `doc(hidden)` types in "the following other types implement trait" diagnostics
Fixes https://github.com/rust-lang/rust/issues/132024.
``@rustbot`` label A-diagnostics T-compiler
clone region obligations instead of taking in implied bounds hack2025-09-30T19:48:55+00:00Jana Dönszelmannjana@donsz.nl2025-09-30T11:29:39+00:00urn:sha1:80e598bb12297c5df04e5b380a4f51aa4dfc5d63Split Bound into Canonical and Bound2025-09-30T16:58:28+00:00jackh726git@jackhuey.me2025-09-28T23:04:55+00:00urn:sha1:d1bbd39c59523d7a5499816a9da200a5910f8b7fRollup merge of #147109 - BoxyUwU:rename_concrete_opaques, r=lcnr2025-09-30T12:25:17+00:00Stuart CookZalathar@users.noreply.github.com2025-09-30T12:25:17+00:00urn:sha1:156d150381ab2e5f2dc2c78eb83b76d7ae95733c
Rename various "concrete opaque type" things to say "hidden type"
r? lcnr
I've found "concrete opaque type" terminology to be somewhat confusing as in conversation and when explaining opaque type stuff to people I always just talk about things in terms of hidden types. Also the hidden types of opaques are very much not *concrete* in the same sense that a type without any generic parameters is concrete which is an unfortunate overlap in terminology.
I've tried to update comments to also stop referring to things as concrete opaque types but this is mostly best effort as it difficult to find all such cases amongst the massive amounts of uses of "concrete" or "hidden" across the whole compiler.
Fix unuseful span in type error in some format_args!() invocations2025-09-30T08:20:51+00:00Tomoaki Kobayashitomoaki.kobayashi.t3@alumni.tohoku.ac.jp2025-09-18T05:42:56+00:00urn:sha1:b13b87a1c3ee3c61b21c4273a87f0b65ccabdde8