rust/tests/ui/traits/next-solver/normalize, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2025-07-20T17:45:01+00:00Consider param-env for fast path2025-07-20T17:45:01+00:00Michael Gouletmichael@errs.io2025-07-20T17:44:55+00:00urn:sha1:1e96d7a55304f8573b6dfeb5ccbdabdb407b89b9tests: add #![rustc_no_implicit_bounds]2025-06-27T05:34:08+00:00David Wooddavid.wood2@arm.com2025-06-27T05:34:08+00:00urn:sha1:1fd13fddba59ab686d5a01c6ad182a5bc109fe00
After reviewing all tests with `?Sized` and discussing with lcnr, these
tests seem like they could probably benefit from
`#![rustc_no_implicit_bounds]`.
tests: bless remaining tests2025-06-16T23:04:35+00:00David Wooddavid.wood2@arm.com2025-02-03T15:54:25+00:00urn:sha1:183458263b0aea42a6ea8b8417117abcae178679
These tests just need blessing, they don't have any interesting behaviour
changes.
Some of these tests have new errors because `LegacyReceiver` cannot be
proven to be implemented now that it is also testing for `MetaSized` -
but this is just a consequence of the other errors in the test.
Structurally normalize types as needed in projection_ty_core2025-05-29T11:16:44+00:00Michael Gouletmichael@errs.io2025-05-28T19:28:11+00:00urn:sha1:2a339ce492349a27c80a0bb9e63510f1798beae1Only prefer param-env candidates if they remain non-global after norm2025-05-07T16:00:21+00:00Michael Gouletmichael@errs.io2025-05-06T20:24:23+00:00urn:sha1:1f774d74b3858154564f8f1609c21f618ba28d96norm nested aliases before evaluating the parent goal2025-04-24T18:41:43+00:00lcnrrust@lcnr.de2025-04-24T02:32:52+00:00urn:sha1:e5e3a95c1e411a76a45283ca6c42671024227301Move `has_self` field to `hir::AssocKind::Fn`.2025-04-14T06:13:04+00:00Nicholas Nethercoten.nethercote@gmail.com2025-04-10T20:28:59+00:00urn:sha1:ce2aa97cd647bdfcb5859489d93526622bb388a0
`hir::AssocItem` currently has a boolean `fn_has_self_parameter` field,
which is misplaced, because it's only relevant for associated fns, not
for associated consts or types. This commit moves it (and renames it) to
the `AssocKind::Fn` variant, where it belongs.
This requires introducing a new C-style enum, `AssocTag`, which is like
`AssocKind` but without the fields. This is because `AssocKind` values
are passed to various functions like `find_by_ident_and_kind` to
indicate what kind of associated item should be searched for, and having
to specify `has_self` isn't relevant there.
New methods:
- Predicates `AssocItem::is_fn` and `AssocItem::is_method`.
- `AssocItem::as_tag` which converts `AssocItem::kind` to `AssocTag`.
Removed `find_by_name_and_kinds`, which is unused.
`AssocItem::descr` can now distinguish between methods and associated
functions, which slightly improves some error messages.
remove `feature(trait_upcasting)` from tests and bless them2025-02-06T22:44:23+00:00Waffle Lapkinwaffle.lapkin@gmail.com2024-12-16T01:29:00+00:00urn:sha1:e9d5d1113f9a5ca0ace2d1b13b1525f43ec97211actually test next solver2024-11-13T17:44:13+00:00lcnrrust@lcnr.de2024-11-13T16:29:38+00:00urn:sha1:117038197db34e7ed2e2683455fcd7dcfc423140normalizes-to disable infer var check2024-10-21T14:25:42+00:00lcnrrust@lcnr.de2024-10-21T14:25:42+00:00urn:sha1:b64b25b99e738f4c68a83f987b203979eaad4fbf