On 11/5/24 03:37, Richard Biener wrote:
On Mon, Nov 4, 2024 at 4:52 PM Andrew MacLeod wrote:
Am 04.11.2024 um 16:32 schrieb Andrew MacLeod :
On 11/4/24 10:27, Richard Biener wrote:
Am 04.11.2024 um 16:01 schrieb Andrew MacLeod :
The invert() range operation is not supported on value
On Mon, Nov 4, 2024 at 4:52 PM Andrew MacLeod wrote:
>
>
> >
> >> Am 04.11.2024 um 16:32 schrieb Andrew MacLeod :
> >>
> >>
> >>> On 11/4/24 10:27, Richard Biener wrote:
> >>>
> > Am 04.11.2024 um 16:01 schrieb Andrew MacLeod :
> The invert() range operation is not supported on values
Am 04.11.2024 um 16:32 schrieb Andrew MacLeod :
On 11/4/24 10:27, Richard Biener wrote:
Am 04.11.2024 um 16:01 schrieb Andrew MacLeod :
The invert() range operation is not supported on values of either VARYING or
UNDEFINED. Primarily this is because UNDEFINED has no type, which make
> Am 04.11.2024 um 16:32 schrieb Andrew MacLeod :
>
>
>> On 11/4/24 10:27, Richard Biener wrote:
>>
Am 04.11.2024 um 16:01 schrieb Andrew MacLeod :
>>>
>>> The invert() range operation is not supported on values of either VARYING
>>> or UNDEFINED. Primarily this is because UNDEFINED
On 11/4/24 10:27, Richard Biener wrote:
Am 04.11.2024 um 16:01 schrieb Andrew MacLeod :
The invert() range operation is not supported on values of either VARYING or
UNDEFINED. Primarily this is because UNDEFINED has no type, which makes it
impossible to perform invert() twice on a value,
> Am 04.11.2024 um 16:01 schrieb Andrew MacLeod :
>
> The invert() range operation is not supported on values of either VARYING or
> UNDEFINED. Primarily this is because UNDEFINED has no type, which makes it
> impossible to perform invert() twice on a value, and produce that same value.
>
The invert() range operation is not supported on values of either
VARYING or UNDEFINED. Primarily this is because UNDEFINED has no type,
which makes it impossible to perform invert() twice on a value, and
produce that same value. There were also times when it wasn't precisely
clear what the c