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
Is it possible to leverage error-prone to develop a system for active refactorings, such as 'rename method', which would then try and perform the error, or give an error if that is not possible (In cases of name collision, or something else)?
Say we want to perform the refatoring 'remove method' on Sub.Do. This wouldn't cause a compile error, since the Do() call would result in calling Super.Do instead of Sub.Do. However, we'd want to instead receive a warning that this refactoring breaks or program.
The text was updated successfully, but these errors were encountered:
Hello,
Is it possible to leverage error-prone to develop a system for active refactorings, such as 'rename method', which would then try and perform the error, or give an error if that is not possible (In cases of name collision, or something else)?
Another example would be
Say we want to perform the refatoring 'remove method' on
Sub.Do
. This wouldn't cause a compile error, since theDo()
call would result in callingSuper.Do
instead ofSub.Do
. However, we'd want to instead receive a warning that this refactoring breaks or program.The text was updated successfully, but these errors were encountered: