Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error message on failed type parse #135

Open
sezna opened this issue Jul 30, 2024 · 0 comments
Open

Better error message on failed type parse #135

sezna opened this issue Jul 30, 2024 · 0 comments
Assignees

Comments

@sezna
Copy link
Collaborator

sezna commented Jul 30, 2024

Currently just throws "expected literal" which is very wrong #111 could help


// TODO: Better error message on failed type parse
// Currently just throws "expected literal" which is very wrong
// https://github.com/ch-systems/petr/issues/111
// ^^ could help
// parse constant literal types, which are just literals


This issue was generated by todo-issue based on a TODO comment in 6c2873b. It's been assigned to @sezna because they committed the code.
@sezna sezna self-assigned this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant