nealrichardson commented on issue #34826: URL: https://github.com/apache/arrow/issues/34826#issuecomment-1503782734
I agree we can do better by using the new tooling. One thing that makes this a little trickier is that usually the error message we're inspecting comes from the Arrow C++ library, where we can't control what class the R error is. I wonder if `cpp11`, or our custom wrapping, could at least add a class to the errors from cpp-land? That way, even if we still need to inspect the original error message to know what to do with it, you could limit that logic to the `cpp_error` class and not `error` in general, so that other kinds of errors would bubble up. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
