Re: Tree-walker callbacks vs -Wdeprecated-non-prototype - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Tree-walker callbacks vs -Wdeprecated-non-prototype
Date
Msg-id CA+hUKGJvX+L3aMN84ksT-cGy08VHErRNip3nV-WmTx7f6Pqhyw@mail.gmail.com
Whole thread Raw
In response to Re: Tree-walker callbacks vs -Wdeprecated-non-prototype  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Tree-walker callbacks vs -Wdeprecated-non-prototype  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
As visible on seawasp and locally (16/main branch nightly packages),
they decided to start warning about these casts with a new strict
variant of the warning.  Their discussion:

https://reviews.llvm.org/D134831

There are also a few other cases unrelated to this thread's original
problem, for example casts involving pg_funcptr_t, HashCompareFunc.  I
guess our options would be to turn that warning off, or reconsider and
try shoving the cast of "generic" arguments pointers down into the
functions?



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Why does L&Y Blink Tree need lock coupling?
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Improve WALRead() to suck data directly from WAL buffers when possible