# E4064

Invalid escape sequence in char/string literal.

## Erroneous example

Using an escape sequence with an invalid Unicode code point results in this
error:

```{literalinclude} /sources/error_codes/4064_error/top.mbt
:language: moonbit
```

Another case is using an unsupported escape sequence in a `Byte` literal:

```{literalinclude} /sources/error_codes/4064_error/top_1.mbt
:language: moonbit
```

Only `\x` and `\o` escape sequences are supported in `Byte` literal.

## Suggestion

Use a valid Unicode code point for `Char` and `String` literals. For `Byte`
literals, use byte escape sequences such as `\x` or `\o`:

```{literalinclude} /sources/error_codes/4064_fixed/top.mbt
:language: moonbit
```