Make ReplaceCut independent from the Cut class

[stwunsch]

Why do we need as input of the ReplaceCut class a Cut object? Wouldn't a tuple like (name, new_cut) be enough? That would be in line with the selection class.

[maxgalli]

Mmm idk honestly, I thought about implementing the double possibility (either a Cut object or a tuple like you said). I wouldn't remove the possibility to pass a Cut object for the simple reason that intuitively, personally, I would be very confused if a class called ReplaceCut doesn't allow to pass a Cut object as an argument. I would be in favor of implementing both (i.e. you can instantiate a variation ReplaceCut either by passing a Cut object or a tuple (new_name, new_expression).

[stwunsch]

the question is whether Cut is a user facing object. so far, it is not, right?