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 parameter completion window currently shows all static and non-static overloads of a method.
This bug can be fixed by adding special checks like what code completion for members does, but I believe the fundamental cause is that the resolver does not check whether the target of an invocation expression is a type or an instance when it does member look up and it gives all the static and non-static members.
I just had a quick look on the resolver and I'm not sure whether I'm right. Hope this info will be helpful.
Has nothing to do with the resolver.
The resolver just resolves - that means that it gives you a type of an AST subtree.
Here the code that "gathers" the information about the stuff the resolver gives - the filtering is done for code completion, but not for parameter completion.
There are several places the resolver "fails" - but it's by design, some things should be handled on another layer.