Copying data between jobs

@TylerMorton

I will update the docs with more details, but to give a bit more in-depth information:

- Invalid: it is an invalid allocation strategy. It is used internally for validation. It shouldn't normally appear in any runtime code other than default-initialized memory or broken code;
- None: it means that the memory the container points to has been allocated somewhere else, and thus the container doesn't own it. It is mostly used internally when we create temporary NativeArrays out of buffers allocated by other means. I'm not sure if we publicly expose any API yet where it makes sense to use Allocator.None;
- Temp: It is a temporary allocation, performed using a very efficient memory allocator. Memory allocated this way is supposed to be used within the current frame and Disposed before the end of it. Referencing memory allocated this way in subsequent frames is invalid and will result in a leak.
- TempJob: It is a temporary allocation, performed using a very efficient memory allocator, specifically tailored for short running Jobs. Memory allocated with TemJob is valid for 3/4 frames after it allocations, so it has to be Disposed earlier than that. Referencing memory allocated this way in subsequent frames is invalid and will result in a leak.
- Persistent: it is a normal persistent native allocation, similar to use malloc on the C++ side (it goes through our optimized native memory allocators, but it is just to give you an idea). The memory allocated this way will have to be disposed manually or will stay allocated forever. This allocation strategy is used for long living allocations.

 

We already extended the docs, written in better Eglish too

The update will be available soon.