Re: simplehash.h: "SH_SCOPE static" causes warnings

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: simplehash.h: "SH_SCOPE static" causes warnings
Date: 2024-04-09 19:56:26
Message-ID: CA+TgmobthdVi7DCA8X6j8z7bTuayG3OHmKFvUVZJfinoJ3LyBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 9, 2024 at 3:33 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> Should I go ahead and commit something like that now, or hold it until
> the other thread concludes, or hold it until the July CF?

I think it's fine to commit it now if it makes it usefully easier to
fix an open item, and otherwise it should wait until next cycle.

But I also wonder if we shouldn't just keep using static inline
everywhere. I'm guessing if we do this people are just going to make
random decisions about which one to use every time this comes up.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-04-09 19:57:28 Re: macOS Ventura won't generate core dumps
Previous Message Robert Haas 2024-04-09 19:53:46 Re: simplehash.h: "SH_SCOPE static" causes warnings