https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68230
--- Comment #8 from Joshua T, Fisher ---
(In reply to Jonathan Wakely from comment #7)
> (In reply to Joshua T, Fisher from comment #5)
> > and my blog where I first encountered this in a closed source codebase:
> >
> > http://www.nullterminated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68230
--- Comment #6 from Joshua T, Fisher ---
(In reply to Joshua T, Fisher from comment #5)
> https://github.com/nvpro-pipeline/VkHLF/commit/b6646c4773e8aef49c40e8684eca1382bf2e9d50
Apologies this one doesn't apply. Just took another look and I just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68230
--- Comment #5 from Joshua T, Fisher ---
(In reply to Jonathan Wakely from comment #2)
> It's rare that my reaction to a -Wunused-parameter warning is to change the
> function to remove the parameter entirely. YMMV.
Totally reasonable, I too rar
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: j.fisher at digipen dot edu
Target Milestone: ---
The code below does not produce a warning when -Wunused-parameter is turned on.
It would be fantastic if it did
