Loop task behaviour is somehow misleading

[gnain]

when the loop task is called like loop(0, 2, <Task>the <Task> is executed 3 times, with indexes 0,1,2 It would be better to have an api with, for instance: loop(, <initialIndex>, <Task>) and maybe another forLoop(<initialIndex>, <maxIndex>, <Task>) // where maxIndex is never reached

[gnain]

@dukeboard You already fixed in v.8 right ?

[dukeboard]

nop i fixed the traverseTimeline bounds but with has right know as well the inclusive semantic. Loop and traverseTimeline are consistent so if we decide to change we should apply it for both