Files
rust/tests/ui/traits
Jonathan Brouwer fc758577be Rollup merge of #153614 - lcnr:find-param-in-clause-ambig, r=BoxyUwU
`FindParamInClause` handle edge-cases

If normalization is ambiguous, we want to treat the where-bound as non-global. The affected code should pretty much always have other errors in that case. It does make reasoning about trait solver cycles and rerunning more confusing and just feels wrong ™️ I encountered this while looking into `ml-kem` (https://github.com/rust-lang/trait-system-refactor-initiative/issues/246). I don't know whether this matters in practice and don't care to look into it too deeply.

We also want to properly handle concrete aliases which mention to something mentioning a generic parameter due to another where-bound.

r? @BoxyUwU
2026-04-02 22:13:52 +02:00
..
2026-03-28 16:18:11 +09:00
2026-02-17 16:51:44 +00:00
2026-03-09 09:11:06 +00:00
2025-12-16 02:10:08 +09:00
2025-07-25 20:38:54 +05:00
2026-03-16 10:21:35 +00:00
2025-06-08 11:25:09 +05:00
2026-02-01 18:20:30 +00:00
2026-02-01 18:20:31 +00:00
2024-10-18 00:33:50 +02:00
2025-08-09 16:27:20 +05:00
2025-07-31 21:25:49 +05:00
2025-08-05 19:34:46 +05:00
2025-08-19 21:27:10 +02:00
2025-08-09 16:27:20 +05:00
2024-04-07 17:38:07 -03:00
2026-03-28 16:18:11 +09:00
2026-03-28 16:18:11 +09:00
2024-03-03 16:30:48 -03:00
2024-03-03 16:30:48 -03:00
2024-03-03 16:30:48 -03:00
2025-12-02 18:25:13 +00:00
2025-02-03 10:39:32 -05:00
2025-12-02 18:25:13 +00:00
2023-12-05 17:15:46 +00:00
2026-03-28 16:18:11 +09:00
2026-03-28 16:18:11 +09:00
2025-08-09 16:27:20 +05:00
2025-11-27 11:19:00 -05:00
2025-11-27 11:19:00 -05:00
2025-11-27 11:19:00 -05:00
2025-06-30 11:50:19 +05:00
2025-06-30 11:50:19 +05:00
2024-01-05 10:00:59 +00:00
2025-08-05 19:34:46 +05:00
2025-08-05 19:34:46 +05:00