We're still not using macros in the 2.10 branch, so this issue will still
happen there. We may do macros later but it's a fair bit of work so I wouldn't
guarantee that it happens in our first 2.10 release.
Matei
On Oct 12, 2013, at 2:33 PM, Mark Hamstra wrote:
> That's a TODO that is either n
That's a TODO that is either now possible in the 2.10 branch or pretty
close to possible -- which isn't the same thing as easy.
On Sat, Oct 12, 2013 at 2:20 PM, Aaron Davidson wrote:
> Out of curiosity, does the Scala 2.10 Spark interpreter patch
> fix this using macros as Matei suggests in the
Out of curiosity, does the Scala 2.10 Spark interpreter patch
fix this using macros as Matei suggests in the linked discussion? Or is
that still future work, but now possible?
On Fri, Oct 11, 2013 at 6:04 PM, Reynold Xin wrote:
> This is a known problem and has to do with peculiarity of the Sca
This is a known problem and has to do with peculiarity of the Scala shell:
https://groups.google.com/forum/#!searchin/spark-users/error$3A$20type$20mismatch|sort:relevance/spark-users/bwAmbUgxWrA/HwP4Nv4adfEJ
On Fri, Oct 11, 2013 at 6:01 PM, Aaron Davidson wrote:
> Playing around with this a l
Playing around with this a little more, it seems that classOf[Animal] is
"this.Animal" in Spark and "Animal" in normal Scala.
Also, trying to do something like this:
class Zoo[A <: *this.*Animal](thing: A) { }
works in Scala but throws a weird error in Spark:
"error: type Animal is not a member o
