Dmitry said:

By the way, a less intrusive solution to this would be grouping/filtering usages by type parameter value in the Find Usages results. What do you think about it?

Some refactorings rely on find usages.

I know rename is one of them, but I always want to rename the class regardless of the type parameter.

What other refactorings are affected by find usages?

If none of them need to be performed differently depending on the type parameter, then the grouping/filtering idea is very good.

There is already a "Find usages" dialog for classes with option checkboxes like "Search for text occurrences". What about adding 2 new checkboxes:

• "Restrict results to usages with matching type parameters" (or something like that)
• "Also search for raw type usages"

The checkboxes would be disabled if the actual type parameter(s) cannot be determined at the search site.