Hi all,
I've noted two of them, but there's probably more:

1) it does not know how to push-up a class side method
2) when pushing up a method, if a sibling has a method of same name
(generally same method, that's why we push up) which invokes super, then
the refactoring override the sibling method with super method!

Example I have class hierarchy A > B > C1, B > C2.
A implements m A>>#m, C1 and C2 also implements m, which ends with a ^super
m.
When I push-up C1>>m into B, I'm told it's impossible to move C1>>m up...
Why not, it's my responsibility, so warning me is good, preventing me is
bad.
But I observed that C2>>m ends-up overwritten with A>>m, and that sucks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200502/12348399/attachment.html>