Brad Chamberlain

Perfect, thanks!

@jabraham17 : Is the concept here to warn whenever a loop zip iterates over distributed and non-distributed things where the non-distributed thing is the leader?

The localSubdomain query works correctly for remote, local arrays: ```chapel var A: [1..10] real; on Locales[1] { writeln(A.localSubdomain()); // prints {1..0}, a degenerate/empty domain } ``` So that might suggest...

I needed a simple coding task to break up the tedium of catching up on backlog, so have a fix for the DR case that seems to be working.

And now I've extended it to distributed arrays as well: https://github.com/chapel-lang/chapel/pull/25754

#25754 is now up for review and should resolve this issue.

Re-opening this since I ended up backing out #25754 for the 2.2 release.

@jeremiah-corrado : The error for the original code doesn't seem completely unreasonable to me since the routine is declared as returning something, being used as though it returns something, yet...

> I think a more helpful error message would be something like: "unable to determine concrete return type for the routine: 'throwsError'". I agree. Or even better might be to...

It looks to me like this is likely due to the `--[dynamic]-auto-local-access` optimization, which is on by default, as turning off either of those optimizations with `--no-dynamic-auto-local-access` or `--no-auto-local-access` seems...