We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Imagine that you have the following classes
ASTA and OCAB OCA And you rename AST -> OC
Therefore the refactoring should check that none of the new names with conflicts because actually doing the refactoring.
@balsa-sarenac I'm tired but I wonder if this is not a nice precondition for such a kind of composition.
The text was updated successfully, but these errors were encountered:
That is really fun example, it should be easily composable, not sure if this is the way it is currently implemented, should check it these days.
Sorry, something went wrong.
No branches or pull requests
Imagine that you have the following classes
ASTA
and OCAB OCA
And you rename AST -> OC
Therefore the refactoring should check that none of the new names with conflicts because actually doing the refactoring.
@balsa-sarenac I'm tired but I wonder if this is not a nice precondition for such a kind of composition.
The text was updated successfully, but these errors were encountered: