Re: Should we remove -Wdeclaration-after-statement? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Should we remove -Wdeclaration-after-statement?
Date
Msg-id CA+TgmoaZRH9vUZgXb0Dk_=9udjXhjQB_0NC50Uo4J99PfyfO+g@mail.gmail.com
Whole thread Raw
In response to Re: Should we remove -Wdeclaration-after-statement?  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Wed, Feb 7, 2024 at 7:55 PM Noah Misch <noah@leadboat.com> wrote:
> > So my suggestion is for people to respond with -1, -0.5, +-0, +0.5, or
> > +1 to indicate support against/for the change.
>
> I'm +1 for the change, for these reasons:
>
> - Fewer back-patch merge conflicts.  The decls section of long functions is a
>   classic conflict point.
> - A mid-func decl demonstrates that its var is unused in the first half of the
>   func.
> - We write Perl in the mixed decls style, without problems.
>
> For me personally, the "inconsistency" concern is negligible.  We allowed "for
> (int i = 0", and that inconsistency has been invisible to me.

This thread was interesting as an opinion poll, but it seems clear
that the consensus is still against the proposed change, so I've
marked the CommitFest entry rejected.

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Catalog domain not-null constraints
Next
From: Robert Haas
Date:
Subject: Re: abi-compliance-checker