Matthew Lutze

@JonathanStarup might be off more help for backend stuff.

Probably related to #4440

I tried doing this by making the stdout etc channels, which seemed to be a nice interface.

``` -- Resolution Error -------------------------------------------------- >> Unexpected non-Java type: 'T'. 5 | new T {} ^ unexpected type. Expected a Java class or interface. ```

This will hopefully not even be necessary if we move JVM resolutions stuff to the Typer.

Marking as blocked until a decision is made about #4392

> ``` > let (x, y) = par (exp, exp) > ``` > > Is also OK, no? I don't like this one because in case `exp` is long and...

> Would it not be more idiomatic to say > > ``` > par (x > following our foreach loop etc? This one seems fine to me

> But, it also nice to write `Node(par (exp, exp, exp))`. How would you support that? Can't we have both? Though it makes the standard de-inline refactoring harder.

> What about par-yield? Also good )