diff options
| author | Eugene Burmako <xeno.by@gmail.com> | 2012-06-07 15:44:04 +0200 |
|---|---|---|
| committer | Eugene Burmako <xeno.by@gmail.com> | 2012-06-08 15:32:46 +0200 |
| commit | bc5f42f51982eb473075bbd2f474a5d628813031 (patch) | |
| tree | a57578c5a21ced5ed38c1a098646fa95ea88f5c2 /lib | |
| parent | 07f7baa21c165d6c2302a8ea26c475968e7d775e (diff) | |
| download | scala-bc5f42f51982eb473075bbd2f474a5d628813031.tar.gz scala-bc5f42f51982eb473075bbd2f474a5d628813031.tar.bz2 scala-bc5f42f51982eb473075bbd2f474a5d628813031.zip | |
removes array tags
Before 2.10 we had a notion of ClassManifest that could be used to retain
erasures of abstract types (type parameters, abstract type members) for
being used at runtime.
With the advent of ClassManifest (and its subtype Manifest)
it became possible to write:
def mkGenericArray[T: Manifest] = Array[T]()
When compiling array instantiation, scalac would use a ClassManifest
implicit parameter from scope (in this case, provided by a context bound)
to remember Ts that have been passed to invoke mkGenericArray and
use that information to instantiate arrays at runtime (via Java reflection).
When redesigning manifests into what is now known as type tags, we decided
to explore a notion of ArrayTags that would stand for abstract and pure array
creators. Sure, ClassManifests were perfectly fine for this job, but they did
too much - technically speaking, one doesn't necessarily need a java.lang.Class
to create an array. Depending on a platform, e.g. within JavaScript runtime,
one would want to use a different mechanism.
As tempting as this idea was, it has also proven to be problematic.
First, it created an extra abstraction inside the compiler. Along with class tags
and type tags, we had a third flavor of tags - array tags. This has threaded the
additional complexity though implicits and typers.
Second, consequently, when redesigning tags multiple times over the course of
Scala 2.10.0 development, we had to carry this extra abstraction with us, which
exacerbated the overall feeling towards array tags.
Finally, array tags didn't fit into the naming scheme we had for tags.
Both class tags and type tags sound logical, because, they are descriptors for
the things they are supposed to tag, according to their names.
However array tags are the odd ones, because they don't actually tag any arrays.
As funny as it might sound, the naming problem was the last straw
that made us do away with the array tags. Hence this commit.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/scala-compiler.jar.desired.sha1 | 2 | ||||
| -rw-r--r-- | lib/scala-library.jar.desired.sha1 | 2 | ||||
| -rw-r--r-- | lib/scala-reflect.jar.desired.sha1 | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/lib/scala-compiler.jar.desired.sha1 b/lib/scala-compiler.jar.desired.sha1 index 022b392187..f92b9d05cc 100644 --- a/lib/scala-compiler.jar.desired.sha1 +++ b/lib/scala-compiler.jar.desired.sha1 @@ -1 +1 @@ -bf1b1d794688e661cd9d94ec42be37515f06f453 ?scala-compiler.jar +cd208e55a800a1b4fcc623f13b44e9df551b617d ?scala-compiler.jar diff --git a/lib/scala-library.jar.desired.sha1 b/lib/scala-library.jar.desired.sha1 index 78e21ae760..b731a1f97e 100644 --- a/lib/scala-library.jar.desired.sha1 +++ b/lib/scala-library.jar.desired.sha1 @@ -1 +1 @@ -9cc8e09873316a58bddef7dc59229ca6e1c27e79 ?scala-library.jar +5d4aa46eabd2a034a3102fb1de168547ef7d977b ?scala-library.jar diff --git a/lib/scala-reflect.jar.desired.sha1 b/lib/scala-reflect.jar.desired.sha1 index cc9ac9405c..5839bf5380 100644 --- a/lib/scala-reflect.jar.desired.sha1 +++ b/lib/scala-reflect.jar.desired.sha1 @@ -1 +1 @@ -ec3636a6da2b3055f6a54488a002a5c3fc2ae192 ?scala-reflect.jar +cebf7edbff7931c4b3d6ef1504b2bf66f1abf6fd ?scala-reflect.jar |