if (!phase.erasedTypes) unique(new UniqueThisType(sym))

[Eugene Burmako]

Stumbled upon this when found out that:

appliedType(ClassTpe, IntTpe) <: appliedType(ClassTpe, IntTpe.erasure) == false

Subtype check fails because erasure transforms ThisTypes for modules into PackageTypeRefs.

Why is this necessary? What else could be unexpectedly changed by erasure? That's important because I use tpe.erasure to build class tags.

[martin odersky]

Lots of things change. Essentially everything that is not a valid Java 1.4 type has to be transformed into one.

 - Martin

[Eugene Burmako]

All right, I've inserted postprocessing that reverts PackageTypeRefs back to ThisTypes, and everything seems to be okay now. 

What else might prevent me from using the result of tpe.erasure in pre-erasure setting? 

[martin odersky]

On Sat, Apr 21, 2012 at 10:19 PM, Eugene Burmako <eugene....@epfl.ch> wrote:

All right, I've inserted postprocessing that reverts PackageTypeRefs back to ThisTypes, and everything seems to be okay now. 

What else might prevent me from using the result of tpe.erasure in pre-erasure setting? 

Why do you need it? I do not think one should do it. It was not planned that way so all bets are off and nobody can guarantee that what you do is correct.

 - Martin 

[Eugene Burmako]

I use it to generate class tags.

[Eugene Burmako]

Also, it's a part of the public API, so imho we should either shut it down or fix it for pre-erasure use.

[martin odersky]

Let's look at it together on Monday. Would 10.30 work for you? -- Martin

--
Martin Odersky
Prof., EPFL and Chairman, Typesafe
PSED, 1015 Lausanne, Switzerland
Tel. EPFL: +41 21 693 6863
Tel. Typesafe: +41 21 691 4967

[Eugene Burmako]

Yep, see you at your office at 10.30.