[Safety System] Schedule 2 jobs in parallel if one modifies an irrelevant part of a struct?

Say I have a struct and 2 jobs like this:

Code (CSharp):

1. struct Vertex
2. {
3.     public float3 position;
4.     public float2 uv;
5. }
6.  
7. struct ColliderJob : IJob
8. {
9.     [ReadOnly] public NativeArray<Vertex> vertices;
10.     [WriteOnly] public NativeReference<PMeshCollider> output;
11.     public void Execute() { /* read from position, ignore UV, write to output */ }
12. }
13.  
14. struct UVJob : IJob
15. {
16.     public NativeArray<Vertex> vertices;
17.     public void Execute() { /* read from position, write to UV */ }
18. }

These jobs should be able to run in parallel since the ColliderJob does not read from the UV field, which is the only thing the UVJob will modify. However the safety system (rightly) complains since I am actually modifying the contents of an array while in use by another job. Is there a way to tell the safety system to just take a chill pill for a bit and not make these jobs depend on one another?

 

Try putting this attribute in front of the vertex array:
[NativeDisableContainerSafetyRestriction]

 

this will trash the cache, as writing the uv invalidates the entire line (false sharing). it may be faster to run them serially.

you should have an array for positions and one for uvs

 

And then another job to combine them into their final form? Hmmm... this might work.