I think this might have been discussed in the past, but I’m interested in hearing updates about future plans for these things.
The most common reason for me not using Entities.ForEach() is when I want to do some once-per-thread logic, like initializing temporary NativeLists in ScheduleParallel jobs, that will live only for the duration of the job. Example of what I imagine:
public class MySystem : SystemBase
{
protected override void OnUpdate()
{
NativeList<int> listForParallelJob;
Entities
.ForThread(() =>
{
// Do something for each thread launched by the job
if(!listForParallelJob.IsCreated)
{
listForParallelJob = new NativeList<int>(Allocator.Temp);
}
})
.ForChunk(() =>
{
// possibility of doing something per chunk
})
.ForEach((Entity entity, ref Translation translation) =>
{
// Use listForParallelJob in some way
})
.ScheduleParallel();
}
}
Can we expect something like this in the future?
Also interested in hearing updates on the IJobEntity discussed in the past. I have cases where I need to operate on too many component types (more than what Entities.ForEach allows) and this new IJobEntity would save me from a ton of boilerplate. Ideally IJobEntity should also give us a “OnBeginThread()” and “OnBeginChunk()”
