Am 19.10.24 um 12:12 schrieb FX Coudert:
Hi Thomas,
Thanks for the clarification. I really hope that it makes it into the standard, > I do not disagree that it is useful, I just really wish we don’t have
to maintain> long-term a lot of nonstandard (or worse,
standard-incompatible) extensions.
Hi Thomas,
Thanks for the clarification. I really hope that it makes it into the standard,
I do not disagree that it is useful, I just really wish we don’t have to
maintain long-term a lot of nonstandard (or worse, standard-incompatible)
extensions. -std=legacy took a lot of ugly work over the
Am 19.10.24 um 10:40 schrieb FX Coudert:
Hi,
As UNSIGNED has been booted off the F202Y list, I think calling it
an extension at this time is fair.
Looks good to me. And yes, calling it an extension is fair.
I apologise, I had missed this piece of information. If UNSIGNED is > not on
track
Hi,
>> As UNSIGNED has been booted off the F202Y list, I think calling it
>> an extension at this time is fair.
>
> Looks good to me. And yes, calling it an extension is fair.
I apologise, I had missed this piece of information. If UNSIGNED is not on
track to becoming a feature in the next sta
On Fri, Oct 18, 2024 at 09:51:21PM +0200, Thomas Koenig wrote:
> Am 18.10.24 um 19:11 schrieb Thomas Koenig:
> > Hello world,
> >
> > I am thinking how to add UNSIGNED to the documentation of the
> > intrinsics. Taking BGT, the alphabetically first one, one
> > could
>
> ... send the e-mail too
Am 18.10.24 um 19:11 schrieb Thomas Koenig:
Hello world,
I am thinking how to add UNSIGNED to the documentation of the
intrinsics. Taking BGT, the alphabetically first one, one
could
... send the e-mail too early.
What I had in mind was something like
@node BGT
@section @code{BGT} --- Bitwi
