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

Age	Commit message (Collapse)	Author	Lines
2022-07-07	On partial uninit error point at where we need init	Esteban Küber	-6/+3
	When a binding is declared without a value, borrowck verifies that all codepaths have one assignment to them to initialize them fully. If there are any cases where a condition can be met that leaves the binding uninitialized or we attempt to initialize a field of an unitialized binding, we emit E0381. We now look at all the statements that initialize the binding, and use them to explore branching code paths that don't and point at them. If we find no potential places where an assignment to the binding might be missing, we display the spans of all the existing initializers to provide some context.
2019-09-06	Fixed grammar/style in error messages and reblessed tests.	Alexander Regueiro	-3/+3

2019-08-05	Make use of possibly uninitialized data a hard error	Tyler Mandry	-0/+46
	This is one of the behaviors we no longer allow in NLL. Since it can lead to undefined behavior, I think it's definitely worth making it a hard error without waiting to turn off migration mode (#58781). Closes #60450. My ulterior motive here is making it impossible to leave variables partially initialized across a yield (see discussion at #63035), so tests are included for that.