Roto has no facilities to create loops. The reason for this is that scripts need to run only for a short time and should not slow down the application. [1]
Wait, what?! Isn't that choice a bit extreme?
There have been plenty of times in scripting where I've needed loops! Am I missing something here?
Hi! That bit of the docs is a bit outdated. We're probably gonna make it optional. The reason for that choice was that the filters for Rotonda need to be very quick and don't really require loops as long as you can do `contains` checks on some lists for example.
So it should probably say "Roto _in Rotonda_ does not have loops". Roto the language as a separate project can then have loops.
Comments
Wait, what?! Isn't that choice a bit extreme?
There have been plenty of times in scripting where I've needed loops! Am I missing something here?
[1] https://rotonda.docs.nlnetlabs.nl/en/stable/roto/00_introduc...
Hi! That bit of the docs is a bit outdated. We're probably gonna make it optional. The reason for that choice was that the filters for Rotonda need to be very quick and don't really require loops as long as you can do `contains` checks on some lists for example.
So it should probably say "Roto _in Rotonda_ does not have loops". Roto the language as a separate project can then have loops.
bosque and fluence aqua also do not have loops (one can loop there, but not in normal sence)