Hi Tagir,
On 1/11/2019 5:32 AM, Tagir Valeev wrote:
On the other hand, from IDE developer point of view, having expression
and statement with so similar syntax definitely adds a confusion to
the parsing (and probably to users). E.g. suppose we want to parse a
fragment which consists of a number
I like it.
There is an advantage to using a visually heavyweight character like ‘#’. If
you don’t want to use that, I think ‘$’ would work.
(I considered ‘%’, but there are two problems: in familiar usage it occurs a
lot in format strings (even more than ‘$’), and moreover in principle the
Received on the -comments list.
> Begin forwarded message:
>
> From: Fred Curts
> Subject: Raw string literals: learning from Swift
> Date: January 11, 2019 at 2:15:10 PM EST
> To: amber-spec-comme...@openjdk.java.net
>
> With Swift 5 recently adding custom String delimiters (also called raw
While I understand where you’re coming from, I think multiple return is likely
to be both more intrusive and less satisfying than it first appears.
First, it’s a relatively deep cut; it goes all the way down to method
descriptors, since methods in the JVM can only return a single thing. So
Received on the comments list.
> Begin forwarded message:
>
> From: Lukas Eder
> Subject: Multiple return values
> Date: January 11, 2019 at 10:57:19 AM EST
> To: amber-spec-comme...@openjdk.java.net
>
> Hello,
>
> I'm referring to the exciting proposed new features around destructuring
>
Hello!
To my personal taste making longer keyword for switch expression is
bad. Expressions should be more compact compared to statements, and
switch expression is already quite verbose (e.g. compared to ?: which
is close to two-case switch expression). So having a separate keyword
like
Received from the -comments list.
> Begin forwarded message:
>
> From: Ben Evans
> Subject: Hyphenated keywords and switch expressions
> Date: January 11, 2019 at 5:19:25 AM EST
> To: amber-spec-comme...@openjdk.java.net
>
> Hi EG members,
>
> I had a couple of comments on hyphenated
