Re: Use pg_icu_unicode_version(void) instead of pg_icu_unicode_version()

From: Joe Conway <mail(at)joeconway(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Use pg_icu_unicode_version(void) instead of pg_icu_unicode_version()
Date: 2026-02-27 14:58:34
Message-ID: e23189c4-efdf-4512-9cf9-0d0d015cc046@joeconway.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/27/26 01:04, Chao Li wrote:
> What I'm interested in is the broader policy: when reviewing
> patches, if we encounter a foo() declaration, should we consistently
> request a change to foo(void)? If yes, the standard should be
> documented somewhere.

Perhaps here?

https://wiki.postgresql.org/wiki/Committing_checklist

--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-02-27 15:03:45 Fix slotsync worker busy loop causing repeated log messages
Previous Message Álvaro Herrera 2026-02-27 14:47:58 Re: Show comments in \dRp+, \dRs+, and \dX+ psql meta-commands