Inconsistency between reference and compiler w.r.t. path patterns resolving to structs

I tried this code:

struct Empty {}

fn test_match(i: i32) -> i32 {
    return match i {
        Empty => 1,
    };
}

I expected to see this happen:
It should fail to compile as Empty should resolve to a struct (path pattern) rather than be interpreted as an identifier pattern.
https://doc.rust-lang.org/stable/reference/patterns.html#r-patterns.path.unqualified "Unqualified path patterns can refer to (...)structs"
https://doc.rust-lang.org/stable/reference/patterns.html#r-patterns.ident.precedent "Path patterns take precedence over identifier patterns."

Instead, this happened:
The code compiled, treating Empty as an IdentifierPattern.

Meta

rustc --version --verbose:

binary: rustc
commit-hash: ded5c06cf21d2b93bffd5d884aa6e96934ee4234
commit-date: 2025-12-08
host: x86_64-unknown-linux-gnu
release: 1.92.0
LLVM version: 21.1.3

Start by reproducing the match expression with rustc and compare its behavior with the Reference sections on unqualified path patterns and identifier-pattern precedence. Trace the compiler's handling of the Empty pattern and add a regression test showing that this code is rejected consistently with the documented rules.