Thanks for the input! The way you describe it working, with buffered iterations playing in a loop, makes sense for a ShapeDiver use of Kangaroo. However, you can imagine that there is significant work to make this happen, as it's very different from the standard ShapeDiver behaviour. Furthermore we don't see a lot of practical applications for it... Which is why we would call this a nice-to-have, but in a somewhat distant future, unless many users demonstrate a strong need.