diff options
author | Eugene Burmako <xeno.by@gmail.com> | 2012-09-12 12:55:39 +0200 |
---|---|---|
committer | Eugene Burmako <xeno.by@gmail.com> | 2012-09-14 13:29:48 +0200 |
commit | f4a722d20547a5b4ffe47405d122b34b586c17c3 (patch) | |
tree | 513b54a5738fbe2d93596461f706eb14f696f404 /tools/cleanup-commit | |
parent | 524c90d09f2fb4687b312f2c7597393978d50b6a (diff) | |
download | scala-f4a722d20547a5b4ffe47405d122b34b586c17c3.tar.gz scala-f4a722d20547a5b4ffe47405d122b34b586c17c3.tar.bz2 scala-f4a722d20547a5b4ffe47405d122b34b586c17c3.zip |
SI-6310 AbsTypeTag => WeakTypeTag
The new name for AbsTypeTag was a matter of a lengthy discussion:
http://groups.google.com/group/scala-internals/browse_thread/thread/fb2007e61b505c4d
I couldn't decide until having fixed SI-6323 today, which is about
trying to reflect against a local class using typeOf.
The problem with local classes is that they aren't pickled, so their metadata
isn't preserved between Scala compilation runs. Sure, we can restore some of
that metadata with Java reflection, but you get the idea.
Before today typeOf of a local class created a free type, a synthetic symbol,
with a bunch of synthetic children that remember the metadata, effectively
creating a mini symbol table. That might be useful at time, but the problem is
that this free type cannot be reflected, because the global symbol table of
Scala reflection doesn't know about its mini symbol table.
And then it struck me. It's not the presence of abs types (type parameters and
abs type members) that differentiates arbitrary type tags from good type tags.
It's the presence of types that don't map well on the runtime world - ones that
can't be used to instantiate values, ones that can't be reflected.
So we just need a name for these types. Phantom types are compile-time only
concept, whereas our types can have partial correspondence with the runtime.
"Weak types" sound more or less okish, so let's try them out.
Diffstat (limited to 'tools/cleanup-commit')
0 files changed, 0 insertions, 0 deletions