lib/error: Keep track of the origin of an error #44

New Issue

BodgeMaster · 2022-08-15T09:43:48+02:00

BodgeMaster commented

2022-08-15 09:43:48 +02:00

Where was it thrown? Did it come from the function I called or was it passed up from another function further down the call stack?

BodgeMaster added the

Enhancement

label 2022-08-15 09:43:48 +02:00

BodgeMaster changed title from ~~lib/error: Add some way to keep track of the origin of an error~~ to lib/error: Keep track of the origin of an error

2022-08-15 09:44:01 +02:00

BodgeMaster commented

2024-01-08 00:57:02 +01:00

Poster

Ideas for that:

for every error, keep track of where it came from using compiler macros (__FILE__ and __LINE__?)
store a pointer to an instance of ErrorOr or ErrorOrVoid somewhere to be passed down with each error
use macros or functions for both instantiating and handling errors to automatically create and clean up the pointer and pass down errors

Ideas for that: - for every error, keep track of where it came from using compiler macros (`__FILE__` and `__LINE__`?) - store a pointer to an instance of ErrorOr or ErrorOrVoid somewhere to be passed down with each error - use macros or functions for both instantiating and handling errors to automatically create and clean up the pointer and pass down errors

Sign in to join this conversation.