This message was deleted.

Not sure what you mean by write and read semantics. Both methods to the same, just that

all

is eager and causes all elements to be realized, thus for example breaking task configuration avoidance, while

configureEach

works lazily. Regarding order, I don't think there is something guaranteed and you should probably not depend on it, even if you know how it currently is.

Given how things work in

TaskContainer

, I interpret

configureEach()

to mean that the

this

object is still being "initialized" (ie. created, but you are still setting its properties), whereas I take

all()

to mean that the

this

object is "fully created" due to its eagerness. Maybe a flawed viewpoint, but probably makes sense in context.

Not really.

all

is simply the old and eager API,

configureEach

the new and lazy API. Other than that, they are equivalent.

Now I have to figure out how to properly reorder the blocks I have due to the lack of distinction. Granted, I have

all()

and

configureEach()

planted on containers that are nominally empty so it should make little difference in practice, but it's the principle of it all if I want all my writes done before my reads, and if

all()

would be "functionally deprecated" in the future.