| Hi Ed,
True enough, but I don't know that I'd necessarily *want* to have this behavior be part of the reference resolution service semantics.
In other words, I see disambiguation as a distinct concept from reference resolution, which in my mind assumes disambiguation has already been performed.
Not that it *couldn't* be supported by reference resolution, though.
What do others think? On Nov 26, 2009, at 2:05 PM, Ed Willink wrote: Hi Robert I'm not sure the reference resolver should support multiple targets - it's intended to go from ref to declaration, and hopefully there's only one declaration of any given entity. I can't think offhand of a language that has multiple *declaration* sites for a given entity. Though if there really are such languages, we could certainly change the IReferenceResolver API to handle that. The UI would presumably pop up a menu allowing the user to select the appropriate destination, if there's a choice.
There may not be many languagers that support multiple declarations in a well-formed program, but when diagnosing a tentative program there may be many candidate declarations to be offered to resolve a user query. e.g is List java.util.List or one of many other List classes?
-- Cheers, - Bob ------------------------------------------------- Robert M. Fuhrer Research Staff Member Programming Technologies Dept. IBM T.J. Watson Research Center
|
