lidavidm commented on issue #28: URL: https://github.com/apache/arrow-go/issues/28#issuecomment-3318400389
https://users.rust-lang.org/t/why-does-std-slice-from-raw-parts-require-a-non-null-pointer-for-zero-length-slices/10534 seems to be the justification for that? When being exported, why can't it become a nullptr? (That said I personally wouldn't be opposed to normalizing this on the Go side on import either.) @pitrou might this have implications for arrow-cpp too? (I suppose arrow-cpp would always ignore the pointer when the allocation is 0-length, though, so there should be no problem.) -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
