(original) (raw)

> That's OK if you think this approach is a better division of  
> concerns (Unsafe being low-level), but in Heap-X-Buffer you are only  
> using Unsafe.get|putXXXUnaligned() and don't consider using  
> get|putXXX directly when unalignedAccess() == true.  

Right, because there's no point in doing so when unalignedAccess() ==  
true because the exact same code will be generated. In my Utopian  
world nothing except Unsafe would have to deal with issues such as  
this. However, I think that people writing library code (e.g. array  
comparison intrinsics) might still need to know.