Description

Fixes: #15510
I think it's introduced by #14653, which changes and/or to match expression.

After looking into compile_match, it's important to collect the value before matching this.

    // Important to collect it first
    builder.push(Instruction::Collect { src_dst: match_reg }.into_spanned(match_expr.span))?;

This pr is going to apply the logic while compiling and/or operation.

User-Facing Changes

The following will raise a reasonable error:

> (nu --testbin cococo false) and true
Error: nu::shell::operator_unsupported_type

  × The 'and' operator does not work on values of type 'string'.
   ╭─[entry #7:1:2]
 1 │ (nu --testbin cococo false) and true
   ·  ─┬                         ─┬─
   ·   │                          ╰── does not support 'string'
   ·   ╰── string
   ╰────

Tests + Formatting

Added 1 test.

After Submitting

Maybe need to update doc nushell/nushell.github.io#1876