RFR: 8215371: Better nodes for concatenated string literals

[Liam Miller-Cushon]

On Fri, Dec 14, 2018 at 1:24 PM John Rose <john.r.rose at oracle.com> wrote:
>
> Slightly more principled solution (along one axis):  Treat string concat
> as a similar form to existing signature-polymorphic methods invokeExact,
> etc.  That treats it as a method call (rather than special control flow or
> block structure), so common method-call code would apply.

That seems like a nice option for supporting the translation
strategies we want, but is potentially less good for the 'IDE-like
tooling' use-case, where tools may not expect concat to be represented
similarly to invocations. Maybe there's room for both approaches? We
could have a higher-fidelity representation in the front-end, and then
lower through a signature-polymorphic invocation.