Draft language spec for JEP 355: Text Blocks
brian.goetz at oracle.com
Mon May 20 23:46:06 UTC 2019
I wonder if we want to be cagey about committing to interning, which is another way to say we must translate too a constant string info. In the future, alternate condy- based representations may seem desirable and we don’t want to be painted into a translation by overspecification.
Sent from my iPad
> On May 20, 2019, at 7:08 PM, Alex Buckley <alex.buckley at oracle.com> wrote:
> Please see http://cr.openjdk.java.net/~abuckley/jep355/text-blocks-jls.html for JLS changes that align with the JEP.
> Text blocks compile to the same class file construct as string literals, namely CONSTANT_String_info entries in the constant pool. Helpfully, the JVMS is already agnostic about the origin of a CONSTANT_String_info, making no reference to "string literals". Therefore, there are no JVMS changes for text blocks, save for a tiny clarification w.r.t. annotation elements.
More information about the amber-spec-observers