New Issue: Can we rename 'forall intents' to 'task intents'?

18463, "bradcray", "Can we rename 'forall intents' to 'task intents'?", "2021-09-25T00:07:11Z"

It's seemed odd for me for some time that we use different terms for
"forall intents" vs. "task intents" given that both concepts share the
same syntax and effectively do similar things. My inclination would be
to call them both task intents since even in a forall loop, they are
affecting behavior on a per-task granularity.

On the other hand, if we were to add intents to for loops (Should we support task intents on `for` loops? · Issue #17857 · chapel-lang/chapel · GitHub)
and foreach loops (no issue currently) as has been proposed, it could
be that "task intent" isn't the right term given that those are implemented
with a single task? "loop intent" could work except that we apply them to
begin and cobegin statements as well. So maybe we need a completely
new term?