Idiomatic foreach schedule

[floral bane]

Is there any plan to make idiomatic foreach to have Entities.ForEach().Schedule() equivalent feature so I dun need to use IJobEntity?

[elfin cloud]

The goal of Idiomatic foreach is to be a nice way to iterate over components on your current thread. As a result, the design goal was never to fake or get around jobs. We tried that with EntitiesForEach, and it ended in long compile times, and people scheduling all the things, even if it would have been quicker on mainthread.

Now, does IJobEntity require slightly more typing? Yes. But the idea is that it should be easy to turn a Idiomatic ForEach into an IJobEntity. Do let us know if you, want better tooling around that! 😄

[floral bane]

I see. Or I ask in other way. Can u make IJobEntity less typing as much as possible that making migrate from Idiomatic foreach to IJobEntity to be as straightforward as possible? Ideally make it almost copy & paste and change almost nothing. 😂

[elfin cloud]

Well, RefRW, and all the others that IFE take in do actually work in IJE now, so you can do something along the lines of copy the <...> part into your execute, and then cut all the names in, and bobs your uncle 😆

[floral bane]

👀 Wow. So I no longer to need to type lots of SystemAPI.GetComponentLookup and ComponentLookup anymore?

[elfin cloud]

SystemAPI inside IJE? not yet, we're currently looking at both side of SystemAPI to see the cost in engineering time when having code that is generated in the way systemapi does it - e.g. how many hours people end up spending on "why does it take a baziliion years to call OnCreate" on my system