For most functions the warning makes sense in strict mode. That's when you should have a clean, finished function with the cruft removed.
The exceptions become painful though: callbacks and #ifdefs. And sometimes when you develop in strict mode, because you will have unused arguments while fiddling with things.
Plus deprecated arguments in APIs, but the compiler already have the deprecate flag to hang that on.