rust/tests/ui/higher-ranked/trait-bounds, branch automation/bors/try https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try 2025-09-30T16:58:28+00:00 Split Bound into Canonical and Bound 2025-09-30T16:58:28+00:00 jackh726 git@jackhuey.me 2025-09-28T23:04:55+00:00 urn:sha1:d1bbd39c59523d7a5499816a9da200a5910f8b7f Region inference: Use outlives-static constraints in constraint search 2025-08-22T11:38:22+00:00 Amanda Stjerna amanda.stjerna@it.uu.se 2025-08-19T10:32:22+00:00 urn:sha1:7dd56b10add80e21514df3a258b02106ebb52245 Revise the extra `r: 'static` constraints added upon universe issues to add an explanation, and use that explanation during constraint blame search. This greatly simplifies the region inference logic, which now does not need to reverse-engineer the event that caused a region to outlive 'static. it's not a borrow checker limitation :< 2025-08-14T15:43:39+00:00 lcnr rust@lcnr.de 2025-08-13T12:08:53+00:00 urn:sha1:3ebf611005370734ddf7ce22e41ac502e4fff59a Use `tcx.short_string()` in more diagnostics 2025-08-07T21:18:00+00:00 Esteban Küber esteban@kuber.com.ar 2025-07-16T19:45:07+00:00 urn:sha1:99196657fcb5c1e20c13e76166c7f52d35584e88 `TyCtxt::short_string` ensures that user visible type paths aren't overwhelming on the terminal output, and properly saves the long name to disk as a side-channel. We already use these throughout the compiler and have been using them as needed when users find cases where the output is verbose. This is a proactive search of some cases to use `short_string`. We add support for shortening the path of "trait path only". Every manual use of `short_string` is a bright marker that that error should be using structured diagnostics instead (as they have proper handling of long types without the maintainer having to think abou tthem). When we don't actually print out a shortened type we don't need the "use `--verbose`" note. On E0599 show type identity to avoid expanding the receiver's generic parameters. Unify wording on `long_ty_path` everywhere. Avoid looking at HIR for trait and impl items 2025-06-30T08:45:43+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-06-13T09:15:35+00:00 urn:sha1:6166cd6b50b9c513ae8f2da45a7f399fd4fcab29 Apply `mismatched-lifetime-syntaxes` to trait and extern functions 2025-06-06T20:27:16+00:00 Jake Goulding jake.goulding@gmail.com 2025-06-06T18:18:32+00:00 urn:sha1:9c6320abb4bbe51f876e5e918a600e9a5c9dd11b Replace `elided_named_lifetimes` with `mismatched_lifetime_syntaxes` 2025-06-04T14:40:04+00:00 Jake Goulding jake.goulding@gmail.com 2025-03-17T16:43:55+00:00 urn:sha1:d35ad948492146f0811d43606db66c65c55980a9 Use more detailed spans in dyn compat errors within bodies 2025-05-27T08:18:11+00:00 Oli Scherer github333195615777966@oli-obk.de 2025-05-26T10:38:02+00:00 urn:sha1:3fff727e87099b6cc4daca13f5fd0adf439ad4e7 Deduplicate dyn compatibility violations due to coercion 2025-05-26T10:57:54+00:00 Michael Goulet michael@errs.io 2025-05-23T11:47:02+00:00 urn:sha1:a59c86ab449ddb83f824b12f87c1e2c6a38399be Avoid extra path trimming in method not found error 2025-05-24T21:31:07+00:00 Noratrieb 48135649+Noratrieb@users.noreply.github.com 2025-05-24T18:22:58+00:00 urn:sha1:01503d0c1e43a23de92ad1577cbdceb7afe47dab Method errors have an extra check that force trim paths whenever the normal string is longer than 10 characters, which can be quite unhelpful when multiple items have the same name (for example an `Error`). A user reported this force trimming as being quite unhelpful when they had a method error where the precise path of the `Error` mattered. The code uses `tcx.short_string` already to get the normal path, which tries to be clever around trimming paths if necessary, so there is no reason for this extra force trimming.