pitrou commented on issue #8: URL: https://github.com/apache/arrow-nanoarrow/issues/8#issuecomment-1203706719
> One way to do this is a bunch of callables that are something like the reverse of SQLite's result interface So this is for building arrays whose type is not strictly known at compile-time? Going through function pointers will make this slower than if you expose type-specific inline functions/macros, at least when appending one items at a time. We have to think about the use cases for nanoarrow. Mostly, it will be used for bridging/converting with non-Arrow systems, and in this scheme people will probably have runtime switch/case statements to dispatch based on datatype anyway. So I'm not sure an untyped convention is really useful. -- 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]
