trinitrix
/
trixy
Archived
5
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(parser/lexing/error): Improve the message of the `NoMatchesTaken` error 

This error should only ever be raised, when we encountered a bug.
This change notifies the user, that the situation is rather likely to be
a bug and that this should be reported.
This commit is contained in:
Benedikt Peetz 2024-03-24 20:03:58 +01:00
parent f14ef1cec2
commit f24d6310fd
Signed by: bpeetz
GPG Key ID: A5E94010C3A642AD
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
trixy-parser/src/lexing/error.rs
View File

@ -41,7 +41,7 @@ pub enum LexingError {
impl AdditionalHelp for LexingError { impl AdditionalHelp for LexingError {
fn additional_help(&self) -> String { fn additional_help(&self) -> String {
match self { match self {
LexingError::NoMatchesTaken => "This token does not produce a possible match".to_owned(), LexingError::NoMatchesTaken => "This is probably a bug, please open an issue at the issue tracker".to_owned(),
LexingError::UnexpectedEOF => "This eof was completely unexpected".to_owned(), LexingError::UnexpectedEOF => "This eof was completely unexpected".to_owned(),
LexingError::ExpectedArrow => "The `-` token is interpretet as a started arrow (`->`), but we could not find the arrow tip (`>`)".to_owned(), LexingError::ExpectedArrow => "The `-` token is interpretet as a started arrow (`->`), but we could not find the arrow tip (`>`)".to_owned(),
LexingError::UnknownCharacter(char) => { LexingError::UnknownCharacter(char) => {