summaryrefslogtreecommitdiff
path: root/build.number.maven
diff options
context:
space:
mode:
authorMartin Odersky <odersky@gmail.com>2012-10-30 20:10:56 +0100
committerMartin Odersky <odersky@gmail.com>2012-10-30 20:12:44 +0100
commit0bb625b7823befafb170ef05f0493dd0a81a217a (patch)
tree9b3f345f0bbc0b6631dc9843d2003f8bd5b1a72c /build.number.maven
parent2c554249fd8e99286134b217027b6e3cb2c92d77 (diff)
downloadscala-0bb625b7823befafb170ef05f0493dd0a81a217a.tar.gz
scala-0bb625b7823befafb170ef05f0493dd0a81a217a.tar.bz2
scala-0bb625b7823befafb170ef05f0493dd0a81a217a.zip
Fixes SI-6500 by making erasure more regular.
With the introduction of value classes, erasure uses specialErasure where a value class C with underlying type T is unboxed to an ErasedValueType. ErasedValue types are eliminated on phase later, in post-erasure. This was done everywhere, except in the parameter types of bridge methods. That was a mistale, because that way bridge methods could not do the boxing/unboxing logic triggered by ErasedValueTypes. Note: there is one remaining use of erasure (not specialErasure) in Erasure.scala. I put in a comment why that is OK.
Diffstat (limited to 'build.number.maven')
0 files changed, 0 insertions, 0 deletions