Better error messages #27

Open
opened 2025-06-11 16:39:08 +00:00 by zyxw59 · 0 comments
zyxw59 commented 2025-06-11 16:39:08 +00:00 (Migrated from github.com)

It would be nice to have more consistent error formatting. As of #24, parse errors contain spans with line and column info, while other errors just contain line numbers. It might be nice for all errors to contain spans, and also to use that info to print out nice errors including the full text of the line in question and markers of where the error occurs.

Additionally, there are a couple errors from expr_parser that just get mapped to the generic "unexpected token" error, and it would be nice to preserve the more specific message for those.

It would be nice to have more consistent error formatting. As of #24, parse errors contain spans with line and column info, while other errors just contain line numbers. It might be nice for all errors to contain spans, and also to use that info to print out nice errors including the full text of the line in question and markers of where the error occurs. Additionally, there are a couple errors from `expr_parser` that just get mapped to the generic "unexpected token" error, and it would be nice to preserve the more specific message for those.
Sign in to join this conversation.
No description provided.