felipecrv commented on issue #2791: URL: https://github.com/apache/arrow-adbc/issues/2791#issuecomment-2859561135
> [arrow-adbc/c/include/arrow-adbc/adbc.h](https://github.com/apache/arrow-adbc/blob/e045731b24f00df50e9c9f50e5ba6ec632cbd3ef/c/include/arrow-adbc/adbc.h#L34-L36) > > Lines 34 to 36 in [e045731](/apache/arrow-adbc/commit/e045731b24f00df50e9c9f50e5ba6ec632cbd3ef) > > /// In general, objects allow serialized access from multiple threads, > /// but not concurrent access. Specific implementations may permit > /// multiple threads. > I think the problem here is more that Rust has no way of knowing whether it is safe or not If thread-safety were a requirement we could perform an unsafe cast on the Rust side. Then thread-safety stops being guaranteed by the Rust type system and becomes guaranteed by the ADBC API requirements and drivers implementing it correctly. -- 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]
