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

Should parse errors be exported? #25

Open
adlai opened this issue Mar 15, 2021 · 1 comment
Open

Should parse errors be exported? #25

adlai opened this issue Mar 15, 2021 · 1 comment

Comments

@adlai
Copy link
Contributor

adlai commented Mar 15, 2021

Betteridge's Law of Headlines states:

If a newspaper headline ends with a question mark, the answer is negative.

GitHub Issues are not newspaper articles, and I have no idea what the correct answer is, although a finer enumeration of the possible malformed documents will almost certainly lead to a situation where the conditions should have their own package(s).

@adlai
Copy link
Contributor Author

adlai commented Feb 26, 2023

see previous griping

My slightly less uneducated guess is that mimicing the overall approach seen in the CL package would be appropriate: major errors all have exported names, some exported names might not be usefully instantiable, and some signalled conditions might not be direct instances of the exported names.

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