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 diagnostics #17

Open
RanolP opened this issue Feb 6, 2022 · 1 comment
Open

Better error diagnostics #17

RanolP opened this issue Feb 6, 2022 · 1 comment

Comments

@RanolP
Copy link
Owner

RanolP commented Feb 6, 2022

Consider beauty diagnostic reporting crates such as:

  • ariadne
  • codespan-reporting
  • annotate-snippets
  • language-reporting
  • miette
@RanolP RanolP mentioned this issue Feb 14, 2022
@RanolP RanolP changed the title Better error report Better error diagnostics Feb 14, 2022
@RanolP
Copy link
Owner Author

RanolP commented Mar 1, 2022

I chose quick-xml because

  • It is a long-lived library
  • It has more stars than others
  • Its features are enough for me

But

  • It is not maintained well. Its latest stable release is about 1 year ago. Also, the repository does not have commits in the past 3 months.
  • it provides poor support for getting error location when using derive macro. So we cannot use the libraries listed above (but actually this problem is widely shared across various libraries).

So we could consider another library. Maybe we could change the language itself (see #22)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant