You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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?
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.)
The text was updated successfully, but these errors were encountered: