jdx/mise · error · eyre::Report

unsupported Go string escape \\{escape}

Error message

unsupported Go string escape \\{escape}

What it means

Error "unsupported Go string escape \\{escape}" thrown in jdx/mise.

Source

Thrown at src/task/workspace/go.rs:243

            'v' => '\u{000b}',
            '\\' => '\\',
            '\'' => '\'',
            '"' => '"',
            'x' => escape_character(&mut characters, 2, 16)?,
            'u' => escape_character(&mut characters, 4, 16)?,
            'U' => escape_character(&mut characters, 8, 16)?,
            digit @ '0'..='7' => {
                let mut digits = digit.to_string();
                for _ in 0..2 {
                    digits.push(
                        characters
                            .next()
                            .ok_or_else(|| eyre::eyre!("incomplete octal Go string escape"))?,
                    );
                }
                decoded_character(&digits, 8)?
            }
            _ => bail!("unsupported Go string escape \\{escape}"),
        };
        unescaped.push(escaped);
    }
    Ok(unescaped)
}

fn escape_character(
    characters: &mut std::str::Chars<'_>,
    length: usize,
    radix: u32,
) -> Result<char> {
    let digits = characters.take(length).collect::<String>();
    if digits.chars().count() != length {
        bail!("incomplete Go string escape");
    }
    decoded_character(&digits, radix)
}

View on GitHub (pinned to 6f52dcdf99)

Solutions

1. Fix the escape sequence in the Go string literal in go.mod/go.work; only standard Go escapes (\n, \t, \xNN, \uNNNN, \\, \") are supported.

When it happens

Trigger: Thrown at src/task/workspace/go.rs:243 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of jdx/mise@6f52dcdf99 (2026-08-22). Data as JSON: /api/errors/f146ca43ab7a93a2. Report an issue: GitHub.