reftable (was: Re: none)

From: Han-Wen Nienhuys <hanwen@google.com>
Date: Nov 22, 2019, 10:38 UTC
Message-ID: <CAFQ2z_PbPEH3=9uJHqXdjV+pxF_-NSS2PGY1ZU-JtxRAuxN66g@mail.gmail.com>
In-Reply-To: <xmqqsgmjb13r.fsf@gitster-ct.c.googlers.com>

On Tue, Nov 19, 2019 at 8:53 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 11 quoted lines

> > I spent the last few weeks cobbling together an implementation of the
> > reftable format in C and in Go. I thought this would be cool to add to
> > git-core, but I doubt whether I will have enough time to see such an
> > effort through. Maybe some of you would want to try integrating it
> > into the Git-core code base?  Example code is here:
> >
> >   https://github.com/google/reftable/blob/master/c/api.h#L153
> >
> > cheers!
>
> My initial impression was that the API overuses typedef.

I changed the code to use struct throughout.

> But the set of operations defined in the header file seemed at the
> right granularity in order to interface with the refs.h & refs/* API
> we have.  It however was unclear to me how transactional ref updates
> would work with it.

I implemented the reftable stack in Go, see

  https://godoc.org/github.com/google/reftable#Stack

which I could implement in C too. Would that work?

-- 
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.