(Damn... Is it "destination"? Or "target"?... Or... "destination"?... F*, naming things is such a chore...)
Since the interactions work with ordered pairs, don't shy away from clearly reflecting that in the nested loop iterator & hook arg names!
(It should feel perfectly natural for modeling interactions involving exchanging entities, like communication, energy/particle transfer etc.)
Having a consistent notion within the engine may help actually utilizing that later, e.g. by adding features on top of that. Also, the app would not have to come up with its own convention. (And it can still ignore the ordering, if it wants; but for symmetric interactions it should really use the lighter loop + callbacks!)
(Damn... Is it "destination"? Or "target"?... Or... "destination"?... F*, naming things is such a chore...)
Since the interactions work with ordered pairs, don't shy away from clearly reflecting that in the nested loop iterator & hook arg names!
(It should feel perfectly natural for modeling interactions involving exchanging entities, like communication, energy/particle transfer etc.)
Having a consistent notion within the engine may help actually utilizing that later, e.g. by adding features on top of that. Also, the app would not have to come up with its own convention. (And it can still ignore the ordering, if it wants; but for symmetric interactions it should really use the lighter loop + callbacks!)