[MonoDevelop] PATCH: More detailed generic paramters for code completion

[Matej Urbas]

Lluis Sanchez wrote:
>> Please, take a look at the attached files, and comment on them (have I 
>> missed the point?).
>>     
>
> It looks much better now. Just a couple of comments:
>
>       * I'm concerned about using generic collections in the public api,
>         since languages which don't support them (does boo have
>         generics?) won't be able to extend it. Maybe using concrete
>         types like this would be enough?:
>         public class TypeConstraintList: List<TypeConstraint> {}
>   
He he, I don't like it, but ok.
>       * Wouldn't TypeConstraint just be an IReturnType (after adding a
>         GenericArguments collection to it)? The same for
>         GenericArgument.
>
>       * Do we need a special handling for naked type constraints? I
>         think we can easily find the declaration of the original generic
>         type.
>   
Ok, if we don't need 'naked' handling of constraints, I'll rework my 
proposal. But we surely need the 'new', 'class' and 'struct' constraints 
in generic parameters...

So, the only thing to change is 'use IReturnType as types'. Roger that!
>   
>> And another thing: It is said that MonoDevelop copied a lot from 
>> SharpDevelop. It was suggested by Gryegory to port whatever they have in 
>> SharpDevelop to MonoDevelop.
>>
>> I'm just interested in what your plans for code assistance were (before 
>> I happened)? As I said, I'm willing to create a plan for code assistance 
>> in MonoDevelop (be it with or without the help of code from SharpDevelop).
>>     
>
> The plan was to wait for somebody interested in working on it. And the
> plan seems to work so far ;-)
>   
A great plan :)
> Reusing code from SharpDevelop is a good thing, ...  ... If there are pieces of SD code which can be integrated in MD without losing the extra features we have (if there are), then go ahead.
>   
Aye.

---
Matt