Re: [PATCH] binary heap implementation - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] binary heap implementation
Date
Msg-id CA+TgmoaS2LkoMs8buhhcQ+OfDuw0yhZYjMrNNKLPNMp6iVSOBg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] binary heap implementation  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [PATCH] binary heap implementation  (Andres Freund <andres@2ndquadrant.com>)
Re: [PATCH] binary heap implementation  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
List pgsql-hackers
On Wed, Nov 21, 2012 at 1:30 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> The following comments still talk about "key and value", thus need
> an update:

Oops.

> This comment needs updated (s/comparator/compare/, and also add
> has_heap_property and arg):

Fixed.

> I would suggest to add prefixes to struct members, so bh_size, bh_space
> and so on.  This makes it easier to grep for stuff later.

OK.

> Do we really need the struct definition be public?  Couldn't it just
> live in binaryheap.c?

Well, that would preclude defining any macros, like
binaryheap_empty().  Since efficiency is among the reasons for
inventing this in the first place, that doesn't seem prudent to me.

Another new version attached.

P.S. to Abhijit: Please, please tell me the secret to getting five
people to review your patches.  I'm lucky when I can get one!

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: add -Wlogical-op to standard compiler options?
Next
From: Robert Haas
Date:
Subject: Re: Doc patch: Document names of automatically created constraints and indexes