Yes, this was deliberate--I originally deleted them entirely, but put them back like this before opening the PR.  For simple methods with a single argument like this, it doesn't matter so much, but this retains the argument name while making it explicitly clear that it's not being used.  For methods with many more arguments, it keeps everything intact even when disabled.

The main reason for this is that it's fixing compiler warnings about unused arguments.  While the arguments are *currently* unused, that's not to say that won't change in the future; for several of the classes, that's guaranteed since they are just disabled since the implementation is currently stubbed out.  When we come to enabling them, it's just a matter of uncommenting.  The alternative is you'll need to dig through the header and/or the parent classes to find out what it was called before you deleted it, so in terms of being able to efficiently work on the code and see what it was that's disabled (and why), I think there's some value in retaining them.  [I originally did remove the entire lot before realising the pain it would cause and adding them back!]