Currently only a limited number of statements/expressions are shown in auto-completion, but I see this as a massive opportunity to support more common Chapel idioms.

Common Idioms

Spawn on task per locale

coforall loc in Locales do on loc {

} 

SPMD: one task per core per locale

coforall loc in Locales do on loc {
   coforall tid in 1..here.maxTaskPar {

   }
}

Data-Parallelism

forall a in A {

}

The iterable used can be based on what is in scope.

@bradcray

Any suggested idioms? I think this is a rather exciting start. @bradcray What do you think are the most useful Chapel idioms?

I believe that you can possibly implement type inference by taking advantage of compilerWarning to obtain the type. For example, imagine you have something like this...

var x : int;
var y = x;
var z = (x + y) : real(32);

How would you get this type information? Like this.

var x : int;
compilerWarning("__TYPE__INFERENCE__ x:", x.type : string);
var y = x;
compilerWarning("__TYPE__INFERENCE__ y:", y.type : string);
var z = (x + y) : real(32);
compilerWarning("__TYPE__INFERENCE__ z:", z.type : string);

TIO

I suggest that the LSP could possibly instrument the original program by adding this to all variable declarations to query their type, which can then be parsed.

@lydia-duncan Any opinions on this approach? Should be a nice and decent short-term solution.