Scala Internals

Did anyone notice this error:

/Users/aleksandar/workspaces/scala/scala/build.xml:1689:
java.lang.RuntimeException: No code.jar found in
/Users/aleksandar/workspaces/scala/scala/test/files/codelib
at scala.sys.package$.error(package.scala:27)
at
scala.tools.partest.nest.PathSettings$$anonfun$srcCodeLib$1.apply(PathSettings.scala:47)
at
scala.tools.partest.nest.PathSettings$$anonfun$srcCodeLib$1.apply(PathSettings.scala:47)
at scala.Option.getOrElse(Option.scala:106)
at
scala.tools.partest.nest.PathSettings$.srcCodeLib(PathSettings.scala:46)
at scala.tools.partest.PartestTask.execute(PartestTask.scala:316)

The consensus seems to be to send this kind of thing to
scala-internals, but I keep forgetting when it comes to messages like
the below. Bet you didn't fully appreciate what was meant by
"-internals", did you!

---------- Forwarded message ----------
From: Paul Phillips
Date: Sun, Feb 5, 2012 at 10:46 PM
Subject: scaladoc

Can we please have some kind of scaladoc mode which does not fail the
build over trivial issues? Or better yet, I'll drop everything to cut
it out of trunk and put it in its own repository, where someone else
can deal with it.  The toll exacted by this sort of thing should have
been unacceptable long ago.

On Sun, Feb 5, 2012 at 8:12 PM, Eugene Burmako wrote:
> Type-level liar?

Something that typechecks iff it doesn't typecheck.

Cheers,

Miles

One thing that I'm finding myself wanting quite frequently these days
is a way of having the compiler verify for me that something otherwise
well-formed doesn't in fact typecheck. The test suite and examples for
shapeless are littered with commented out lines like,

  def acceptOption[L <: HList : TC[Option]#λ](l : L) = true

val l1 = Option(23) :: Option(true) :: Option("foo") :: HNil
  val l2 = Option(23) :: true :: Option("foo") :: HNil

 acceptOption(l1)  // Compiles
 //acceptOption(l2)  // Does not compile

which is pretty useless if I should ever break things in such a way
that the last line actually _did_ compile.

Is there something that quasiquotation could do for us here?

Subj

Hi,

I was working on https://issues.scala-lang.org/browse/SI-64 lately, and I would like to get some feedback on my (partial) implementation.

The code can be found at https://github.com/szabolcsberecz/scala/tree/SI-64 (fjbg must be recompiled first)

On Fri, Feb 3, 2012 at 7:25 AM, Grzegorz Kossakowski
wrote:
> Is sbt anywhere soon hitting master? Indeed, it has a chance to make those
> things easier to cope with.

I decided to engage the bull by the horns and throw off the bits of
bull which have kept me on ant to this point. There may be too much
bull in the bathwater for some tastes, but it's a starting point.

New branch!

https://github.com/scala/scala/tree/sbt-core

It's the regular build, with stuff commented out and more probably to
follow, whittling down to my core interest: the transformation of
scala source code located in a couple specific directories into food
suitable for consumption by jvms.

Hi!

From the notes: