https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=cargo_update 2025-09-26T14:37:08+00:00 2025-09-26T14:37:08+00:00 lcnr rust@lcnr.de 2025-09-26T14:37:03+00:00 urn:sha1:c2e39c2f20c568b96fe89c751e65bbbe9116231c 2025-09-26T14:33:15+00:00 lcnr rust@lcnr.de 2025-09-23T15:33:24+00:00 urn:sha1:148fd9ad3c434c26a952e01e37c35aa26cb8315c 2025-09-18T13:49:53+00:00 bors bors@rust-lang.org 2025-09-18T13:49:53+00:00 urn:sha1:4cd91ef8223ef54111d21aa9e9e71b3b26477dd3 `-Znext-solver` allow `ExprKind::Call` for not-yet defined opaques Based on https://github.com/rust-lang/rust/pull/146329. Revival of rust-lang/rust#140496. See the comment on `OpaqueTypesJank`. I've used the following document while working on this https://hackmd.io/Js61f8PRTcyaiyqS-fH9iQ. Fixes https://github.com/rust-lang/trait-system-refactor-initiative/issues/181. It does introduce one subtle footgun we may want to handle before stabilization, opened https://github.com/rust-lang/trait-system-refactor-initiative/issues/230 for that. Also cc https://github.com/rust-lang/trait-system-refactor-initiative/issues/231 for deref and index operations r? `@BoxyUwU` 2025-09-18T10:58:38+00:00 lcnr rust@lcnr.de 2025-09-11T11:08:36+00:00 urn:sha1:f4e19c68786211f3c3cf2593442629599678800a 2025-09-17T23:37:35+00:00 Cameron Steffen cam.steffen94@gmail.com 2025-09-16T22:08:14+00:00 urn:sha1:9ecca51bbe151c4ce0e374c46d1a0bfd1ec63d49 2025-09-15T09:02:12+00:00 tiif pekyuan@gmail.com 2025-09-15T09:02:12+00:00 urn:sha1:1c30399ceae2400e266660a8f98a7504c284fda1 2025-09-09T12:49:16+00:00 Boxy rust@boxyuwu.dev 2025-08-21T15:50:54+00:00 urn:sha1:e379c7758667f900aaf5551c4553c7d4c121e3e1 2025-09-08T19:39:36+00:00 bors bors@rust-lang.org 2025-09-08T19:39:36+00:00 urn:sha1:9c27f27ea3bab79a2fec827ef3ae0009959d60f4 eagerly compute `sub_unification_table` again Previously called `sub_relations`. We still only using them for diagnostics right now. This mostly reverts rust-lang/rust#119989. Necessary for type inference guidance due to not-yet defined opaque types, cc https://github.com/rust-lang/trait-system-refactor-initiative/issues/182. We could use them for cycle detection in generalization and it seems desirable to do so in the future. However, this is unsound with the old trait solver as its cache does not track these `sub_unification_table` in any way. We now properly track the `sub_unification_table` when canonicalizing so using them in the new solver is totally sound and the performance impact is far more manageable than I thought back in rust-lang/rust#119989. r? `@compiler-errors` 2025-09-08T12:17:56+00:00 lcnr rust@lcnr.de 2025-09-08T09:41:43+00:00 urn:sha1:b51a3a565a056235f3864e2cefdb9449f6b0dcb1 2025-09-08T12:17:56+00:00 lcnr rust@lcnr.de 2025-08-27T07:42:09+00:00 urn:sha1:f51458640840cb94c32f1e55431b1c855ca22e88