You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We observed the following case of function invocations in the original code used for synthtic dataset: an method extrMethod(); is called from different places (different methods) within the same class. This is a case of code duplication. It may be that the reason extrMethod was defined as a separate method is precisely because of code duplication, and not because it is a semantically cohesive piece of code which can serve as a good example of ExtractMethod refactoring.
What we want
Eliminate the factor of code duplication in our synthetic dataset on LM/EM.
Proposed solution
Simplest and least nuanced solution: do not inline methods that are invoked more than once with a give class.
The text was updated successfully, but these errors were encountered:
Why
We observed the following case of function invocations in the original code used for synthtic dataset: an method extrMethod(); is called from different places (different methods) within the same class. This is a case of code duplication. It may be that the reason extrMethod was defined as a separate method is precisely because of code duplication, and not because it is a semantically cohesive piece of code which can serve as a good example of ExtractMethod refactoring.
What we want
Eliminate the factor of code duplication in our synthetic dataset on LM/EM.
Proposed solution
Simplest and least nuanced solution: do not inline methods that are invoked more than once with a give class.
The text was updated successfully, but these errors were encountered: