On Sat, 4 Feb 2023, 21:23 Christopher Bazley, wrote:
>
>
> On Sat, 4 Feb 2023 at 20:40, Jonathan Wakely
> wrote:
>
>>
>> On Sat, 4 Feb 2023, 17:01 Christopher Bazley via Gcc,
>> wrote:
>>
>>>
>>> Does the lack of support for Clang's nullability qualifiers in GCC
>>> indicate
>>> a greater likel
Snapshot gcc-12-20230204 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20230204/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sat, 4 Feb 2023 at 20:40, Jonathan Wakely wrote:
>
> On Sat, 4 Feb 2023, 17:01 Christopher Bazley via Gcc,
> wrote:
>
>>
>> Does the lack of support for Clang's nullability qualifiers in GCC
>> indicate
>> a greater likelihood for my proposed feature to be accepted into GCC?
>
>
> No, I don't
On Sat, 4 Feb 2023, 17:01 Christopher Bazley via Gcc,
wrote:
>
> Does the lack of support for Clang's nullability qualifiers in GCC indicate
> a greater likelihood for my proposed feature to be accepted into GCC?
No, I don't think so. I think it would be better to support the same
qualifiers as
In August, I had an idea for a C language extension to improve null pointer
safety. The tl;dr is that whereas a pointer-to-const may have undefined
behaviour on write access, a pointer-to-_Optional may have undefined
behaviour on read or write access. I shared this proposal with my
colleagues, many
