If I understand the proposal correctly, you can do
export session.{ call1 => _, _ }
Yes indeed. I think that’s the best solution. Lightweight and makes clear what gets generated.
My main reservation against automatically suppressing forwards on conflicts are the possible surprises. “Why did it not install an alias for this method? Oh it’s because a method with the same name is inherited through this sequence of traits!” That’s the kind of surprises we know from inheritance that we want to avoid here.