+1
Yes, supporting switch expressions would make a big improvement I would
think even if not exactly the same as Java.
On Mon, Aug 10, 2020 at 11:28 PM Milles, Eric (TR Technology) <
eric.mil...@thomsonreuters.com> wrote:
> The current state of Java's switch expression is described briefly here:
>
On 10.08.20 12:57, Paul King wrote:
Hi Everyone,
Any other updates/comments before I submit our latest board report? (Due
in a couple of days)
gcontracts falls in August, thus would be part of the next report?
bye Jochen
Correct. I would say that this quarter's "planning for GContracts" falls
under "planning our roadmap for Groovy 4" but I was going to refrain
from more specific details until the next quarter where it's worth a
specific mention.
Cheers, Paul.
On Mon, Aug 10, 2020 at 9:41 PM Jochen Theodorou
The current state of Java's switch expression is described briefly here:
https://docs.oracle.com/en/java/javase/13/language/switch-expressions.html
They are a stepping stone to introducing pattern matching. First step is
statement -> expression and multi case. This new syntax creates a gap
Hi,
this is Brian Goetz initial idea
https://cr.openjdk.java.net/~briangoetz/amber/pattern-match.html
And these are the related JEPs
https://openjdk.java.net/jeps/361
https://openjdk.java.net/jeps/375
and this is the umbrella project amber
https://openjdk.java.net/projects/amber/
cheers
- Leo
+1
Remko.
> On Aug 10, 2020, at 19:57, Paul King wrote:
>
>
>
> Hi Everyone,
>
> Any other updates/comments before I submit our latest board report? (Due in a
> couple of days)
>
> Thanks, Paul.
>
> ===>8==
>
> ## Description:
> Apache Groovy is responsible for
