- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Scala Meeting report, 2010-04-20
Tue, 2010-04-27, 10:48
We are currently publishing a summary of each of the weekly meetings of the
Scala Core Team.
This information is made available as a service to the community. It is by
necessity rather brief and gives only a rough approximation of the main
points of discussions explored during each meeting; it should not be taken
as a source of reliable information, nor as a record of concrete or firm
decisions, nor as anything other than a record of a simple discussion.
The summary that follows is primarily intended for Scala contributors and
maintainers. If you are not a contributor to the Scala system, the
information below is unlikely to be very useful to you, and you might lack
some of the necessary background to make sense of all the discussion items.
We do not have enough people on the team to be able to write a more
complete record, and we might also not have the resources to discuss every
point in detail afterwards. Nevertheless, we hope that this record, cursory
as it is, is better than nothing.
------------------------------------------------------------------------------
Scala Meeting 2010-04-20
People attending the meeting: Lukas, Martin, Gilles, Philipp, Iulian,
Tiark, Ingo, Alex, Hubert, Phil, Donna, Miguel, Adriaan, Toni. Special
guests: Pedro Furlanetto, Josh Suereth, Nathan Bronson, Mushtaq Ahmed.
* Current work
- non-null verification
- scaladoc tweaks, fixed many scaladoc bugs
- work on reflection
- work on specialization
- general bugfixing
* Scala 2.8
- RC1 has problems with specializations. Should be fixed in a few days,
then we will have a RC2 release. Will test building other Scala projects
first (e.g., ScalaTest).
- Testing our release: we probably should build Lift, ScalaTest, maybe
others. Josh will help us setting up a hudson job for building Lift and its
dependencies.
- Possibly give a date before which the final won't be shipped (so that
people have time to test out an RC without crazy hack sessions).
- partest still has issues; this needs to be fixed before next RC process.
* Specialized methods
- There is a new scheme for typing specialized methods, having to do with
not always typechecking erased types then re-typechecking with
specialization. The new scheme avoids compiler exceptions when, under
erasure, types would have worked out anyway.
* ScalaDays
- We will have a meeting to consolidate the notes we took during the
community discussion session.
- next Scala Days: LinkedIn and Stanford are interested in helping with
organization, but details are still unclear.