A scenario that is common enough: moving ClassA.Method<T>() to become ClassB<T>.Method() and vice versa.
Would be nice to update the call sites by moving the type parameters spec between method/class, to avoid breaking the code.
Description
A scenario that is common enough: moving ClassA.Method<T>() to become ClassB<T>.Method() and vice versa.
Would be nice to update the call sites by moving the type parameters spec between method/class, to avoid breaking the code.
Presented case is not common enoght to be included in move refactoring.
Heavy UI is required to map source method's parameters to the target class parameters.
For now usages can easily be updated by inlining of following method:
Method<T>(T t)
{
ClassB<T>.Method(t);
}
Code of method have to be moved manually or inlined in the target class:
Method(T t)
{
ClassA.Method<T>(t); <- inline here
}
Sergey Shkredov - 07 Feb 08 21:16 Presented case is not common enoght to be included in move refactoring.
Heavy UI is required to map source method's parameters to the target class parameters.
For now usages can easily be updated by inlining of following method:
Method<T>(T t)
{
ClassB<T>.Method(t);
}
Code of method have to be moved manually or inlined in the target class:
Method(T t)
{
ClassA.Method<T>(t); <- inline here
}
Usability Problem
Open
Normal
Refac::CS::MoveStaticMember: Should Support Moving a Generic Method into a Generic Class, and Vice Versa
Heavy UI is required to map source method's parameters to the target class parameters.
For now usages can easily be updated by inlining of following method:
Method<T>(T t) { ClassB<T>.Method(t); }Code of method have to be moved manually or inlined in the target class:
Method(T t) { ClassA.Method<T>(t); <- inline here }