alamb commented on issue #2362: URL: https://github.com/apache/arrow-rs/issues/2362#issuecomment-1209203156
> My point above is, we have certain checks for it during performing value validation, in the places we want to make sure the data is valid (safe paths, 😄 ). So it will be caught nowadays. I agree with @viirya I think perhaps we were using different definitions of "unsound" . I was erroneously thinking it meant "unsafe" in the classic rust sense that doing so would allow reading/writing uninitialized memory, reading/writing out of bounds of the allocated memory, or data races. It *doesn't mean* that user's can't provide bad inputs that result in `Err` or `panic!`, though I think many rust libraries try and do thorough error checking and uphold strong invariants I think it is a good idea to make the arrow library be better about error checking in general as long as it isn't too cumbersome to use. Thank you @HaoYang670 for starting this conversation -- 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]
