// JOBS.  HOW DO THEY WORK??
//
//1) We need a struct that extends IJob...
//implementing Execute, that does not use any unity methods inside, just does "stuff" on data like math!
//2) In some main thread method, create the job with new, set the data it needs and then
//call job.Schedule
//job.Schedule will send the job to a main thread to be executed at it's own pace.
//Then in late update, (or somewhere after).  Call job.Complete() and copy the data we computed on back into unity classes or whatever we want to do with it.
//Complete FORCES the job to complete, by dedicating MAIN THREAD time to it until it is done. This is blocking, but useful if you are scheduling a job every frame
//If you have a job that you don't want to block, and can be finished "whenever it's had enough time to finish" (all on the non-main thread). You can listen for job.IsComplete in Update or something, and it will be set to true whenever the job has finished.  At this point you need to call Complete() to finalize it.
/You can ONLY access the (processed) data on your job once you've called Complete(), so you HAVE to call it at some point before accessing your data



public class JobTest:MonoBehaviour {

    public List<TestJob> j = new List<TestJob>();
    public List<JobHandle> jh = new List<JobHandle>();
    public System.Diagnostics.Stopwatch s;


    void Update() {
        TestJob tj = new TestJob() {
            someDataWeNeed = 10;
        };

        j.Add(tj);
//batch size can't be too big or too small, too small = slower, too many iterations to do.  too big = slower, too many executes to do per batch
        jh.Add(tj.Schedule());



    }
    public void LateUpdate() {
        for(int i = 0; i < jh.Count; i++) {
            jh[i].Complete();
        }


    }

    [BurstCompile]
    public struct TestJob:IJob{

        public int someDataWeNeed;

        public void Execute() {
            someDataWeNeed= someDataWeNeed++;

        }
    }

}