Le 21/02/2021 à 01:05, Wes McKinney a écrit : > I agree that we should avoid leaking uninitialized memory in places > where we have control over it. I could imagine a third party project > having UBSAN warnings and then tracing the origin of them to something > in Arrow that they then have to work around. As for the potential > performance implications, we'll have to be vigilant with > microbenchmarks.
We're generally already doing this when we're careful, so we're already paying the price (which I would estimate intuitively quite small). Unfortunately, there doesn't seem to be an obvious way to check it systematically on CI, but Valgrind can occasionally uncover it. Regards Antoine.
