Error handling

[johnchronis]

Google released a library for returning and handling error messages some time ago. Now that hustle is growing maybe such a solution would be beneficial to make the code cleaner and handling/propagation of errors easier. We had discussed this in the past, but never went through with it (this library was not available at the time).

You can find more information here: https://abseil.io/docs/cpp/guides/status

What do you think? Would such a convention for error handling play nice with arrow?

[kpgaffney]

Nice idea! Arrow has a status as well. Our error codes could be a superset of Arrow’s. Not sure about compatibility but I’m guessing we could write some utility functions to make it easier to go back and forth between the two types.