From: Jacob Keller <jacob.keller@gmail.com>
Date: Fri, 19 Aug 2016 22:02:12 GMT
Subject: Re: [PATCH v8 7/8] cache: add empty_tree_oid object
Message-ID: <CA+P7+xparEBHc-nrqYQoadg+dedD90qjLUBWiekhOYst_+0fsA@mail.gmail.com>
In-Reply-To: <xmqqtwegzckf.fsf@gitster.mtv.corp.google.com>

On Fri, Aug 19, 2016 at 2:14 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Jacob Keller <jacob.keller@gmail.com> writes:
>>
>>> Is there a reason for that? I've found that .field = value is safer
>>> because it ensures that you don't end up initializing the wrong
>>> values? Or is it a compatibility thing?
>>
>> Yes.
>
> That was a bit too terse.  The answers to all three questions are
> "Yes", "Yes", and "Yes".
>
> Together with enum ... = { A, B, C, }; we may want to consider not
> worrying about ancient compilers at some point, and it might be this
> year or next year, but I do not think we want to do that as part of
> this series.

Thanks, it makes sense. It is hard to remember when some feature got added.

Regards,
Jake