Esteban Küber 0f82cfffda Keep track of patterns that could have introduced a binding, but didn't ... When we recover from a pattern parse error, or a pattern uses `..`, we keep track of that and affect resolution error for missing bindings that could have been provided by that pattern. We differentiate between `..` and parse recovery. We silence resolution errors likely caused by the pattern parse error. ``` error[E0425]: cannot find value `title` in this scope --> $DIR/struct-pattern-with-missing-fields-resolve-error.rs:19:30 | LL | println!("[{}]({})", title, url); | ^^^^^ not found in this scope | note: `Website` has a field `title` which could have been included in this pattern, but it wasn't --> $DIR/struct-pattern-with-missing-fields-resolve-error.rs:17:12 | LL | / struct Website { LL | | url: String, LL | | title: Option<String> , | | ----- defined here LL | | } | |_- ... LL | if let Website { url, .. } = website { | ^^^^^^^^^^^^^^^^^^^ this pattern doesn't include `title`, which is available in `Website` ``` Fix #74863.		2024-12-13 21:51:33 +00:00
..
src	Keep track of patterns that could have introduced a binding, but didn't	2024-12-13 21:51:33 +00:00
Cargo.toml	rustdoc: update to pulldown-cmark 0.11	2024-06-30 18:33:48 -07:00
messages.ftl	Diagnostic for using macro_rules macro as attr/derive	2024-11-22 16:49:10 +00:00