Imported From: https://issues.scala-lang.org/browse/SI-7699?orig=1
Reporter: @paulp
See #2568, #7475

@paulp said:
Note that if both are private, it compiles. If both are private[s], it fails, but at least it fails understandably and in a way which can be resolved (though the failure to compile is still a bug if the specification is supposed to have any relevance.)

./a.scala:5: error: class Y1 inherits conflicting members:
  value m in trait B1 of type String  and
  value m in trait B2 of type String
(Note: this can be resolved by declaring an override in class Y1.)
class Y1 extends s.B1 with s.B2  // compiles
      ^

@retronym said:
Possibly related to #7475

@paulp said:
They are related, but what's at issue here is that we don't mangle package-private or object-private members at all, which means they are not private. In #7475 it is attempting to do the right thing by mangling the private member, but the implementation has bugs -- whereas here we are not even trying to do the right thing.

package s {
  object o {
    trait A {
      private[this] val m1 = 1
      private       val m2 = 2
      private[A]    val m3 = 3
      private[o]    val m4 = 4
      private[s]    val m5 = 5
    }
    // Here is what that produces:
    // public abstract int s$o$A$$m1();
    // public abstract int s$o$A$$m2();
    // public abstract int s$o$A$$m3();
    // public abstract int m4();
    // public abstract int m5();
  }
}

@adriaanm said:
Duplicate of #261