Possible Bug in NativeList and RemoveAtSwapBack?

I am currently tinkering with implementing an A* pathfinding algorithm with ECS. I am using a JobSystem with an IJobChunk for this. I am not sure, if this will get me the maximum efficiency, but that's what I am working on. I have made the strange observation, that when I use NativeList.RemoveAtSwapBack, it changes the order of my List elements, with elements at the back suddenly being transported to the front. I first thought, that it was my A*-implementation doing bollocks, but now that I have implemented my own RemoveAt-function, it works fine. Is there someone else, who can confirm, that this is an issue, or maybe point me, what I am doing wrong?

My code (with the replaced RemoveAt) is the following: https://pastebin.com/kSTSY0C2

 

As per the description in https://docs.unity3d.com/Packages/com.unity.collections@0.0/api/Unity.Collections.NativeList-1.html

"Truncates the list by replacing the item at the specified index with the last item in the list. The list is shortened by one."

 

This is exactly the intended functionality. RemoveAtSwapBack performs a faster remove by removing the element at the index and then moving the last element to the index of the removed item. To maintain order of the elements you would need to shift a number of elements equal to (count - 1 - index) which for very long lists could be very slow.

 

I am truly sorry. I totally missed that. Thanks for the insight. I now have to rethink my code.