Question CollectionHelper CreativeNativeArray vs new

Is there any functional difference between

Code (csharp):

1.  
2. NativeArray< EntityAndPositionData > workArrayVersion1 = CollectionHelper.CreateNativeArray< EntityAndPositionData , RewindableAllocator >(
3.    _workEntityQuery.CalculateEntityCount() , ref World.UpdateAllocator ) ;
4.  
5. // alternative way to make a list ?benefits between the two ?
6. NativeList< EntityAndPositionData > workArrayVersion2 = new NativeList< EntityAndPositionData >( _workEntityQuery.CalculateEntityCount() , Allocator.TempJob ) ;
7.  

 

There's quite a big difference. Different container types. Different allocators. Different lifetime guarantees. Different disposal responsibilities. You get the idea.

 

Ah I meant

Code (csharp):

1.  
2. NativeArray< EntityAndPositionData > workArrayVersion1 = CollectionHelper.CreateNativeArray< EntityAndPositionData , RewindableAllocator >(
3.    _workEntityQuery.CalculateEntityCount() , ref World.UpdateAllocator ) ;
4.  
5. NativeArray< EntityAndPositionData > workArrayVersion2 = new NativeArray< EntityAndPositionData >( _workEntityQuery.CalculateEntityCount() , Allocator.Temp ) ;
6.  

but point taken about all the other differences, thanks.

 

As far as I understood it the first variant allows you to provide a custom allocator (like World.UpdateAllocator) while the second variant only works with the usual allocator labels (at least for NativeArray).

 

Pretty much. And you only really need CollectionHelper for NativeArray. Everything in the Collections package works with custom allocators via ToAllocator.