paleolimbot commented on issue #598: URL: https://github.com/apache/arrow-adbc/issues/598#issuecomment-2231756148
I'd like to pick this up soon since it would be very helpful for driver authors to do low level tests on their implementations like: https://github.com/apache/arrow-adbc/blob/8ea1ce1381c0110c7e0f4edea0774ba1543f4a2c/c/driver/common/driver_test.cc#L68 One could also go even further and make something that is ergonomically C++-y, but my immediate use case is something portable that doesn't involve a driver author managing C memory. This is vaguely how writing nanoarrow C++ works: there are still some C function calls, but no C memory management. > There is a question of what to do with errors in Release(); One could either have some "Session" that has a trash can for unreleasable objects (and/or a mechanism for a notice/warning that this has happened), or just stderr and leaking the object (which is probably sufficient for testing). -- 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]
