rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-09-28	reword note	Esteban Küber	-2/+2

2025-09-28	Point at lifetime requirement origin in more cases	Esteban Küber	-2/+2

2025-09-28	Point at fn bound that introduced lifetime obligation	Esteban Küber	-0/+2
	``` error[E0597]: `c` does not live long enough --> $DIR/without-precise-captures-we-are-powerless.rs:19:20 \| LL \| fn simple<'a>(x: &'a i32) { \| -- lifetime `'a` defined here ... LL \| let c = async move \|\| { println!("{}", *x); }; \| - binding `c` declared here LL \| outlives::<'a>(c()); \| ---------------^--- \| \| \| \| \| borrowed value does not live long enough \| argument requires that `c` is borrowed for `'a` LL \| outlives::<'a>(call_once(c)); LL \| } \| - `c` dropped here while still borrowed \| note: requirement that `c` is borrowed for `'a` introduced here --> $DIR/without-precise-captures-we-are-powerless.rs:7:33 \| LL \| fn outlives<'a>(_: impl Sized + 'a) {} \| ^^ ``` When encountering a `ConstraintCategory::Predicate` in a funtion call, point at the `Span` for that `Predicate` to explain where the lifetime obligation originates from.
2025-01-06	`best_blame_constraint`: don't filter constraints by sup SCC	dianne	-2/+2
	The SCCs of the region graph are not a reliable heuristic to use for blaming an interesting constraint for diagnostics. For region errors, if the outlived region is `'static`, or the involved types are invariant in their lifetiems, there will be cycles in the constraint graph containing both the target region and the most interesting constraints to blame. To get better diagnostics in these cases, this commit removes that heuristic.
2024-11-22	Stabilize the 2024 edition	Eric Huss	-1/+0

2024-11-09	Dont suggest use<APIT>	Michael Goulet	-0/+15

2024-10-31	Try to point out when edition 2024 lifetime capture rules cause borrowck issues	Michael Goulet	-0/+190