/loops are an unnecessary abstraction over /goals, created to force a buzzword into existence
a /loop is effectively the same thing as a /goal, because the model can create its own stopping condition and decide when to stop. at least in most implementations
a /goal can achieve the same result as a /loop if the stopping condition is open-ended. i do this all the time with /goal
in theory:
/loop find dead code and delete it
should be better than:
/goal find dead code and delete it
because /goal would more or less require finding all the dead code first in order to precisely define the “all” stopping condition , while /loop can stay open ended and keep searching for dead code
the problem is that:
- as i said,
/goalcan already do this with an open-ended stopping condition /loopcan still give itself a stopping condition anyway and decide to stop at any time
so in practice, /loop doesn’t really add anything meaningful. it is just /goal for retards