- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Scala Meeting report, 2010-01-12
Wed, 2010-01-13, 20:53
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.
------------------------------------------------------------------------------
Report from the Scala Core Team meeting, 2010-01-12:
People attending the meeting: Hubert, Martin, Eugene, Phil, Alex, Tiark,
Adriaan, Lukas, Toni, Gilles, Iulian, Philipp.
* Current work
- work on .net compiler and integration package for Visual Studio
- parallel arrays, fixed bugs and added methods for array access
- probabilistic analysis for vector concatenation: finally having a
workable model
- work on immutable.Map, experimented with using map structure for
general relations.
- .NET / IKVM
- inlining fixes
- actors benchmarking
- refining partial function with better types
- build manager
- more profiling for compiler performance
* 2.8.0 Beta
- a number of issues were fixed subsequently to the release of RC7,
including #2364, #2883, and the slow `classPath.findClass`. Among the open
issues: #2880, #2876, #2877, #2865.
- in general, it seems that none of those is a showstopper; further,
more betas/RCs will follow after this initial release.
- consensus: we will call RC7 the beta. We will post a message asking
whether any critical problems should stop us from releasing.
* Eclipse
- The Eclipse plugin might require more frequent updates with respect to
the beta releases of the compiler.
- We will create a separate stream of releases for the plugin, which can
be released more often. The update site will be made available together
with the beta. Miles will indicate which revisions should be included in
the update site.