Thread safety, Allocator.Temp,

How is thread safety enforced when using ParallelForTransform?

"The C# Job System solves this by sending each job a copy of the data it needs to operate on, rather than a reference to the data in the main thread. This copy isolates the data, which eliminates the race condition."

This is fine for arrays of floats, but there is ParallelForTransform. Once I have a transform I can write code such as transform.gameObject.GetComponent<X>() and from there I can call functions in a non-threadsafe way. Is it intended that I'm responsible for my own thread-safety in this case, such as by using critical section locks?

"Allocator.Temp has the fastest allocation. It is for allocations with a lifespan of one frame or fewer"
Within the same frame or until the next frame? What qualifies as a frame, is that Update() to Update()?

In RaycastCommand.ScheduleBatch it says "The first invalid result is identified by the collider being null" However, what about if I wait several frames before checking the results, and an earlier collider in the array had been destroyed for other reasons? I would have other valid results but wouldn't know it.

 

Don't missing first part:
If maxHits is larger than the actual number of results for the command the result buffer will contain some invalid results which did not hit anything. The first invalid result is identified by the collider being null.

All this paragraph only about maxHits which anyway not working yet, and only returns first hit.

 

I'd like to clarify, from a transform I can get a component, and from there I can call any code in my entire game. Is it doing some kind of code analysis and automatically locking critical sections based on that?