Re: Documenting coding style - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Documenting coding style
Date
Msg-id adkOBpMyt0A6ki5U@nathan
Whole thread Raw
In response to Documenting coding style  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, Apr 10, 2026 at 10:17:44AM -0400, Andres Freund wrote:
> On April 10, 2026 3:57:56 AM EDT, Thomas Munro <thomas.munro@gmail.com> wrote:
>> I thought we agreed to stop using Size for new code?  size_t has been
>> around since C89.
> 
> We really need to start documenting some of this stuff somewhere.
> Deciding something a few years ago, deep in a thread, won't actually help
> anyone but the participants (and maybe not even them) to know about it..

I certainly didn't know this.  There's no comment in c.h, either.

> I wonder if we should move the coding style section out of sgml into a
> top-level CODING_STYLE.md or something like that.
> 
> And then obviously add things like Size being deprecated. 

Unless we're going to actually remove the typedef in the near future, I'm
not sure I'd support even marking it deprecated.  If we're going to keep it
around indefinitely, that's just going to become another source of nitpicks
when new contributors inevitably copy/paste some code from the aughts.  A
style page makes the situation a little better, but it's yet another thing
that folks have to remember.

To be clear, if someone proposed a patch that completely removed all traces
of Size, I'd likely support it.  There is indeed no reason not to use
size_t.  (I see that Size has been an alias for size_t since 1998 [0].)
But it's also quite heavily used, so I'd be fine with leaving it around and
considering it fully supported, too.

[0] https://postgr.es/c/0ad5d2a3a8

-- 
nathan



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Use XLogRecPtrIsValid() instead of negated XLogRecPtrIsInvalid
Next
From: Daniil Davydov
Date:
Subject: Re: Fix bug with accessing to temporary tables of other sessions