diff options
author | Eugene Burmako <xeno.by@gmail.com> | 2013-04-03 17:46:16 +0300 |
---|---|---|
committer | Eugene Burmako <xeno.by@gmail.com> | 2013-04-03 19:38:07 +0300 |
commit | 34a6fa9bb44ffd96dbb0ee59905fecf4e29879ba (patch) | |
tree | 8d8b2fa639449f560a508b29a56b1b3c3f57d6bc /test/disabled | |
parent | 00fcd46ed0ed3e981e241c8b5458ba821294c669 (diff) | |
download | scala-34a6fa9bb44ffd96dbb0ee59905fecf4e29879ba.tar.gz scala-34a6fa9bb44ffd96dbb0ee59905fecf4e29879ba.tar.bz2 scala-34a6fa9bb44ffd96dbb0ee59905fecf4e29879ba.zip |
SI-6937 core type tags are no longer referentially unique
Type tag factory used to evaluate the provided type creator in the
context of the initial mirror in order to maintain referential equality
of instances of standard tags. Unfortunately this evaluation might fail
if the mirror provided doesn't contain the classes being referred to.
Therefore I think we should avoid evaluating type creators there.
Note that failure of evaluation doesn't mean that there's something
bad going on. When one creates a type tag, the correct mirror /
classloader to interpret that tag in might be unknown (like it happens
here). This is okay, and this is exactly what the 2.10.0-M4 refactoring
has addressed.
Something like `res2.typeTag[A].in(currentMirror)` should be okay.
Diffstat (limited to 'test/disabled')
0 files changed, 0 insertions, 0 deletions