Re: Cleanup shadows variable warnings, round 1
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Peter Eisentraut <peter@eisentraut.org>, Peter Smith <smithpb2250@gmail.com>
Date: 2026-04-21T11:02:44Z
Lists: pgsql-hackers
On Tue, 21 Apr 2026 at 19:02, Chao Li <li.evan.chao@gmail.com> wrote: > PFA v8 - rebased and fixed a few new occurrences. Which of these are new to v19? Can you separate those ones out? IMO, we should commit at least those, as those won't cause any backpatching pain. I recall that I was motivated to commit the -Wshadow=compatible-local ones as there'd been a few bugs with shadowed variables. There'd be more of an argument to cause all this churn if it was for something more than to make things better for clang users. David
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix new-to-v19 -Wshadow warnings
- 4f0cbc6fb5df 19 (unreleased) landed
-
Reduce scope of for-loop-local variables to avoid shadowing
- cece37c9843c 19 (unreleased) landed
-
Fix local-variable shadowing in pg_trgm's printSourceNFA().
- cdaa67565867 19 (unreleased) cited