As I noticed by the broken CI build there was a huge commit on 24th of July, which brought unnested packages to Scala. It seems, I missed something important. What is the point an semantics of these changes?
Here, scala.List(3,4,5) looks for my.scala.List(3,4,5), and gives a
compile error.
After that commit:
package my.scala.stuff
Here, scala.List(3,4,5) gets _root_.scala.List, and works fine.
Suppose I _want_ scala.List to be my.scala.List:
package my
package scala.stuff
Here, scala.List(3,4,5) looks for my.scala.List(3,4,5).
A large recent thread on imports in the scala-user thread gives some
background. I expect someone else is typing a better explanation up.
2009/7/29 Ilya Sergey :
> Hi all.
>
> As I noticed by the broken CI build there was a huge commit on 24th of July,
> which brought unnested packages to Scala. It seems, I missed something
> important. What is the point an semantics of these changes?
>
> With best regards,
> Ilya
>
Before that commit:
package my.scala.stuff
Here, scala.List(3,4,5) looks for my.scala.List(3,4,5), and gives a
compile error.
After that commit:
package my.scala.stuff
Here, scala.List(3,4,5) gets _root_.scala.List, and works fine.
Suppose I _want_ scala.List to be my.scala.List:
package my
package scala.stuff
Here, scala.List(3,4,5) looks for my.scala.List(3,4,5).
A large recent thread on imports in the scala-user thread gives some
background. I expect someone else is typing a better explanation up.
2009/7/29 Ilya Sergey :
> Hi all.
>
> As I noticed by the broken CI build there was a huge commit on 24th of July,
> which brought unnested packages to Scala. It seems, I missed something
> important. What is the point an semantics of these changes?
>
> With best regards,
> Ilya
>