Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10068#issuecomment-161043614
Certainly that fixes the obvious issue here. Is a single call to
`_UNSAFE.copyMemory` safe in this respect? for example imagine moving a copying
a big block of memory where dst = src - 1. Maybe a unit test or two to cover
the case you're fixing and these corner cases too?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
