It can be made pluggable, of course. I don’t want to have that there in a way
that it requires
the refactoring engine to be present all the time.
If it’s there —> transform. If not —> do what it does now.
But just think how much this simplifies the experience of people loading old
code into a new
Pharo version: it just keeps running and fixes itself! It’s that kind of things
we need to be
able to evolve the system.
Imagine, this is a functionality (I think) no other system has!
Yes but we should make it pluggable.
I would like something that says
before all the tests were green and after these automatic changes they
are also green :)
I will not like a feature where it transforms my code without asking.
I would prefer that a diff browser pops up and asks me if changes are ok.
Automatic rewrite of code often forgot to check some specific cases and you end
with bugs in your code if there is no review.
The idea is great but the choice of changing the code or not has to be in the
user hands.
