Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | While working on partest discovered that Compil... | Paul Phillips | 2010-03-25 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | While working on partest discovered that CompilerCommand ignores half its constructor arguments and a couple dozen places blithely pass it those arguments as if they're being used. Then there were setups like this: class OfflineCompilerCommand( arguments: List[String], settings: Settings, error: String => Unit, interactive: Boolean) extends CompilerCommand(arguments, new Settings(error), error, false) Hey offline compiler command, why throw away the perfectly good settings you were given? Ever heard 'reduce, reuse, recycle'? How did you ever work... or do you? No review. | ||||
* | Enabled scalacheck tests. | Paul Phillips | 2010-03-01 | 1 | -1/+1 |
| | | | | | | | | what must be legacy scalatest.* properties to partest.*, boldly assuming that the fact that partest is pretty much unusable outside of scalac means there are no users outside of scalac who might be disrupted by eliminating old property names. Review by community. | ||||
* | Disabled docgenerator test, which isn't compati... | Gilles Dubochet | 2009-11-24 | 1 | -0/+295 |
Disabled docgenerator test, which isn't compatible with Scaladoc 2. |