> De: "Brian Goetz"
> À: "Remi Forax"
> Cc: "Gavin Bierman" , "amber-spec-experts"
>
> Envoyé: Mardi 9 Avril 2019 21:14:25
> Objet: Re: switch statement and lambda
> I see why this is tempting, but I am going to suggest we wait. As
completed
this analysis, I’m reluctant to add more special cases.
> On Apr 9, 2019, at 3:10 PM, fo...@univ-mlv.fr wrote:
>
>
>
> De: "Gavin Bierman"
> À: "Remi Forax"
> Cc: "amber-spec-experts"
> Envoyé: Mardi 9 Avril 2019 19:28:57
>
> De: "Gavin Bierman"
> À: "Remi Forax"
> Cc: "amber-spec-experts"
> Envoyé: Mardi 9 Avril 2019 19:28:57
> Objet: Re: switch statement and lambda
>> On 6 Apr 2019, at 21:17, Remi Forax < [ mailto:fo...@univ-mlv.fr |
>> fo...@un
> On 6 Apr 2019, at 21:17, Remi Forax wrote:
>
> Currently this code doesn't compile
> IntConsumer c = x -> switch(x) { default -> System.out.println(x); };
>
> I believe it should because this is the basic pattern for supporting the
> actor model,
> you consume a message and do a side
Currently this code doesn't compile
IntConsumer c = x -> switch(x) { default -> System.out.println(x); };
I believe it should because this is the basic pattern for supporting the actor
model,
you consume a message and do a side effect* depending on the type of the
message,
translated in Java,
