Interop: deal with namespace clashes

[FroMage]

In Java you can write a class, method, property and field with the same name because they are in a different namespace. This isn't true in Ceylon, so we need to find a strategy around it:

class Foo {
 class a {}
 int a; 
 int getA(){ return 0; }
 void a(){}
}

[gavinking]

I would be inclined to think that this one is a very low priority. I have never seen this kind of thing in practice.

[FroMage]

Good point, moving it off M2, we can always reschedule if we end up needing it sooner.

[FroMage]

Sort-of related is #337, where we have an issue with Java fields (or JavaBean properties) named hash or string, because they conflict with our erasure to hashCode() and toString() and cannot be considered as overriding them.

[FroMage]

M5.

[FroMage]

Moving to M6

[FroMage]

This depends on ceylon/ceylon-spec#833 and as such is moved to 1.1

[FroMage]

Moving to 1.2

[vietj]

We do have this Java API:

  NetSocket ssl(Handler<Void> handler);
  boolean isSsl();

This shadowing prevents us obtaining the ssl property value.