Scala Internals

A gentle reminder... deadline for submitting to the Scala Days is 22nd February (ie Wednesday, next week)
Full details on how to submit a talk can be found at:
  http://days2012.scala-lang.org/node/101

I'm sure I'm not the only person saddled with a bunch of git branches based on svn about which we/I feel daily generalized anxiety.
Oh look, adriaan has 363 branches, he'll make a nice test case.
  # adriaan's  https://github.com/adriaanm/scala-my-svn  # mine after running a couple programs  https://github.com/adriaan-less/scala-your-svn
The programs I ran are "git-remaster" and "git-branches-remaster" found here:

Hi,

is it possible to change the class name of Ctrie to something more in line with the style guide out there?
Having "ConcurrentHashMap" in Java I think "ConcurrentTrie" is a reasonable choice. Imho it is very dangerous to not follow the standard naming without a very good reason, because it serves as precedent and excuse for users to ignore naming conventions in their own code.

Scala Style guide:

Classes should be named in the camelCase style with the very first letter of the name capitalized [...] This mimics the Java naming convention for classes.

Hello,

Maybe this is not the correct place to post this, let me know if there is a better place.
I created a compiler plugin that allows you to get information about a property that is accessed. An example:
object X {
   val y:String = "z"
   test(y)
   def test(metadata:Metadata) = {       println(metadata) //Metadata(y,class java.lang.String,X$@5f9849e5)
   }
}

Is it possible to assign symbols to idents without distorting the
structure of the original AST? Also, would this "symboled" method
require Context? (because in the reifier we don't have a typechecking
context)

On Feb 15, 5:55 pm, Paul Phillips wrote:
> On Wed, Feb 15, 2012 at 8:49 AM, Eugene Burmako wrote:
>
> > No, I don't actually rely on typechecking being performed in-place. The
> > only thing I need is having symful originals, which can be achieved in
> > multiple ways.
>
> I wonder if we should have an explicit "symboled" method.  That's what
> enterXXX does, plus or minus, but it would make more sense to me if the
> overall mechanism more closely  paralleled the typer.

On Wed, Feb 15, 2012 at 8:04 AM, Lukas Rytz <lukas [dot] rytz [at] epfl [dot] ch> wrote:

Regarding comment found here: https://github.com/scalamacros/kepler/commit/f617469164

+       *  To the moment I know only one such situation: typedAnnotations does not typecheck the annotation in-place, but rather creates new trees and typechecks them, so the original remains symless.
+       *  This is laboriously worked around in the code below. I hope this will be the only workaround in this department.

Hi,
I'd like to propose a few changes to how we organize our issue tracking.