l(|projs|
        matches!(projs.first().unwrap().kind, ProjectionKind::Field(..)))assertion failed: !is_completely_captured || (captured_by_move_projs.len() == 1)expected this to be `()`return type inferred to be `assertion failed: !args.has_infer() && !args.has_placeholders()cannot resolve opaque typeassertion failed: !hidden_ty.has_infer()user args: unexpected inference variable after writeback: assertion failed: value <= 0x7FFF_FFFFUse of unknown address space Do not know how to get HirId out of Rvalue and StaticItem with expression doesn't evaluate to a structfound byte string literal with non-ref type binding cannot be both mutable and by-referencecannot borrow as mutable inside an `&` patternreplace this `&` with `&mut`struct pattern resolved to tuple struct pattern resolved to assertion failed: opt_slice_ty.is_some() || slice.is_none()unit struct, unit variant or constantunit structunexpected pattern resolution: ` is interpreted as , not a new bindingbind the struct field to a different name insteadconstants only support matching by type, if you meant to match against a range of values, consider using a range pattern like `min ..= max` in the match blockother_introduce a new binding insteadunexpected resolution for path pattern: only `char` and numeric types are allowed in range patternsIn a match expression, only numbers and characters can be matched against a range. This is because the compiler checks that the range is non-empty at compile-time, and is unable to evaluate arbitrary comparison functions. If you want to capture values of an orderable type between two end-points, you can use a guard.Impossible, verified above.emit_err_pat_range: no side failed or exists but still error?parameterbindingto declare a mutable to take parameter `` by reference, move `&` to the typeconsider removing `&` from the pattern` cannot be dereferencedThis error indicates that a pointer to a trait type cannot be implicitly dereferenced by a pattern. Every trait defines a type, but because the size of trait implementors isn't fixed, this type has no compile-time size. Therefore, all accesses to trait types must be through pointers. If you encounter this error you should try to avoid dereferencing the pointer.

You can read more about trait objects in the Trait Objects section of the Reference: https://doc.rust-lang.org/reference/types.html#trait-objectsunexpected pattern type first introduced with type `in the same arm, a binding must have the same type in all alternativesstruct pattern is not an ADTa field named `fields named these field` has a field named `This error indicates that a struct pattern attempted to extract a nonexistent field from a struct. Struct fields are identified by the name used before the colon : so struct patterns should resemble the declaration of the struct type being matched.

If you are using shorthand field patterns but want to refer to the struct field by a different name, you should rename it explicitly. and inaccessible fieldsfields pattern does not mention  and ignore the inaccessible fieldsinclude the missing field in the pattern