You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gilles, am opening this ticket for you since it came up in email between martin and me and we didn't want it to slip through the cracks. I am willing to implement it if you like but I could use a sketch of how you think I ought to go about it.
ClassManifest.scala:
defsubargs(args1: List[OptManifest[_]], args2: List[OptManifest[_]]):Boolean= {
(args1 zip args2) forall {
case (x: ClassManifest[_], y: ClassManifest[_]) => x <:< y // !!! [Martin] this is wrong, need to take variance into accountcase (NoManifest, NoManifest) =>truecase _ =>false
}
}
The text was updated successfully, but these errors were encountered:
@xeno-by said:
Scala 2.10.0-M3 includes type tags (which may be renamed by the time 2.10.0-final hits). Type tags are thin wrappers over compiler's Types, which means that they support all intricacies of Scala's type system.
Type tags are now a recommended way to reify types, and manifests are deprecated. Hence we won't invest into fixing bugs in manifests, especially such deep as this one.
Malcolm Greaves (malcolmgreaves) said:
There's a glaring fault with TypeTags in 2.10 though: they are not threadsafe. This makes them useless for nearly any production system. Are TypeTags going to be fixed on 2.10?
Gilles, am opening this ticket for you since it came up in email between martin and me and we didn't want it to slip through the cracks. I am willing to implement it if you like but I could use a sketch of how you think I ought to go about it.
ClassManifest.scala:
The text was updated successfully, but these errors were encountered: