commit
this.
Thanks!
-Erich
From: Keane, Erich
Sent: Friday, December 14, 2018 2:57 PM
To: Richard Smith
Cc: cfe-commits
Subject: RE: r349201 - Add extension to always default-initialize nullptr_t.
Thanks! I’ll take a look in a bit!
-Erich
From: Richard Smith [mailto:rich...@metafoo.co.uk
Thanks! I’ll take a look in a bit!
-Erich
From: Richard Smith [mailto:rich...@metafoo.co.uk]
Sent: Friday, December 14, 2018 2:55 PM
To: Keane, Erich
Cc: cfe-commits
Subject: Re: r349201 - Add extension to always default-initialize nullptr_t.
Attached. With the functional part of your change
on of a CK_LValueToRValue in
>> the case where it’s a read from nullptr_t
>>
>>
>>
>>
>>
>> *From:* Richard Smith [mailto:rich...@metafoo.co.uk]
>> *Sent:* Friday, December 14, 2018 2:41 PM
>> *To:* Keane, Erich
>> *Cc:* cfe-commits
>> *S
gt;
>
> *From:* Richard Smith [mailto:rich...@metafoo.co.uk]
> *Sent:* Friday, December 14, 2018 2:41 PM
> *To:* Keane, Erich
> *Cc:* cfe-commits
> *Subject:* Re: r349201 - Add extension to always default-initialize
> nullptr_t.
>
>
>
> Sorry, I was late with my review c
Reverted in r349206.
From: Richard Smith [mailto:rich...@metafoo.co.uk]
Sent: Friday, December 14, 2018 2:41 PM
To: Keane, Erich
Cc: cfe-commits
Subject: Re: r349201 - Add extension to always default-initialize nullptr_t.
Sorry, I was late with my review comment. I think this is the wrong way
, Erich
Cc: cfe-commits
Subject: Re: r349201 - Add extension to always default-initialize nullptr_t.
Sorry, I was late with my review comment. I think this is the wrong way to
approach this problem. This does not "fix all situations where nullptr_t would
seem uninitialized", and it mak
Sorry, I was late with my review comment. I think this is the wrong way to
approach this problem. This does not "fix all situations where nullptr_t
would seem uninitialized", and it makes our AST representation lose source
fidelity.
On Fri, 14 Dec 2018 at 14:25, Erich Keane via cfe-commits <
cfe-c
