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

Error handling discussion #66

Open
martinfouilleul opened this issue Apr 7, 2024 · 1 comment
Open

Error handling discussion #66

martinfouilleul opened this issue Apr 7, 2024 · 1 comment
Assignees

Comments

@martinfouilleul
Copy link
Collaborator

Think about better and more systematic error surfacing mechanisms (eg use handles to carry errors / collect errors when we log them and allow to inspect them? etc.)

@bvisness
Copy link
Sponsor Collaborator

This would probably be a good one to discuss in person at a meeting. My general feeling though is that we should come up with an error scheme that can map reasonably well to the richer error-handling schemes in newer programming langauges.

I don't know exactly what that looks like, but having some kind of explicit error types behind the scenes, with some kind of handle system for the C API, seems like it could be a reasonable place to start?

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

4 participants