Brad Chamberlain

I think I'd take the approach of giving each argument its own line, with its description (if present) following it in a different font by default; and then have a...

Thanks for the work here, @jeremiah-corrado! And thanks for filing this, @ninivert—let us know if you have any feedback!

I've wordsmithed a little to reduce the implication that you literally proposed this.

I think it's inevitable that we're going to want to add new keywords to the language, to avoid being stuck without anywhere to go in terms of adding new features...

> p.s. @lydia-duncan's over suggestion above is completely new to me and arguably doesn't have some of those negative side effects that mapped has. Oh, I'd completely forgotten about that...

Thinking some more about `over` last night, I found myself wondering whether it was a less-good match for layouts, e.g.: ```chapel const D = {1..100, 1..100} over new columnMajorOrder(); var...

Thinking about other preopositional(ish)/"innocuous" English words after being reminded of `mapped`, `using` came to mind: ```chapel const D = {1..n} using new blockDist({1..n}); const D = {1..100, 1..100} using new...

Continuing to spitball with the "innocuous words" idea, this time focusing on ones already in the lexer: ```chapel const D = {1..n} as new blockDist({1..n}); const D = {1..100, 1..100}...

Yeah, I had that same reaction, but have been trying not to set these up for failure or success, just curious how people react. Arguably worse than your case is...

@e-kayrakli : I hate to say it, but I think I'm seeing another mis-application of the auto-local-access optimization (possibly equivalent to the previous one… it's Friday afternoon, so I'm thinking...