Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
The "Unused parameter" warnings show for methods used as delegates and event handlers. This is noise, it isn't helpful, since as a consumer of events and delegate-based APIs you have no control over what you get passed.
Ok that's difficult :/
@light: I think generally that can't be solved in a code issue.
But let's try:
The problem is that methods that aren't private could be used as delegates/event handlers outside of the current file - and analyzing the project scope is more or less out of scope of the code issues.
(I consider it too costly - but maybe someone tries it out)
But it's arguable that classes should expose methods used as delegates/event handlers by other classes - therefore I've just made a simple approach by collecting all methods used as delegates/event handlers and never add an issue for them - light can you check the commit ?
Yes, the commit is fine.
I'm just worrying there may be other tricky problems with this issue. For example, now it only ignores method overrides, but it may also need to ignore virtual/abstract methods since a parameter may only be used in overrides.