[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Coalescing operator
From: |
Paolo Redaelli |
Subject: |
Re: Coalescing operator |
Date: |
Mon, 04 Jul 2022 09:29:58 +0200 |
User-agent: |
K-9 Mail for Android |
Il 3 luglio 2022 20:33:26 CEST, Raphael Mack <ramack@raphael-mack.de> ha
scritto:
>Am Freitag, dem 01.07.2022 um 10:14 +0200 schrieb Paolo Redaelli:
>> Il 30/06/22 18:41, Hans Zwakenberg ha scritto:
>> > What would happen if neither of the two arguments in your example
>> > is void? Which of the two would be printed?
>>
>> None, it would trigger a call to void exception if the first argument
>> is
>> Void.
>
>I guess you misread the question. It was about both being NON-Void.
>Then the second would be printed.
>
>But clearly illegal would be if the first one w/could be Void ad this
>would always be the target for the "or" call.
Ooops, you're right 😅
("Foo" or "bar").is_equal("bar")
33 or 42 = 42
Using is_default instead of Void works for both expanded and reference types.
The diff is really small, I'll save it for a later time.
--
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.