Consider two jobs, and one native array. The first job writes to the first half of the native array, and the second half writes to the second half. Naturally, the job system is going to complain that the two jobs interfere, and that a dependency should be created. The job system has no idea that one job will only write to certain indexes, and so it naturally complains because safety is not provable. This makes sense, but a natural workaround does not. Instead of having the jobs write directly to the native array, how about they each get a slice of the native array to write to? In that way, one declares specifically which indexes the jobs can write to. They can only write into the slice they are given, and even if that slice is backed by the same native array as another slice another job is writing to, there should not be any issue if the slices do not contain any of the same elements. Unfortunately, the job system still complains in this situation. The job system seems to *always* consider it unsafe if the slices are backed by the same array, even if none of the slices overlap with any of the other slices. The information is there inside of the slice declarations, I think it would be extremely useful for the job safety system to take advantage of that.