| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | t5717: test message, not just absence of compiler crash | Lukas Rytz | 2017-04-07 | 1 | -1/+1 |
| | | |||||
| * | unset inappropriate execute bits | Seth Tisue | 2015-09-02 | 1 | -0/+0 |
| | | | | | | | | | | | I imagine these date back to old Subversion days and are probably the result of inadvertent commits from Windows users with vcs client configs. having the bit set isn't really harmful most of the time, but it's just not right, and it makes the files stand out in directory listings for no reason | ||||
| * | SI-5717 error when bytecode cannot be written | Som Snytt | 2013-03-22 | 1 | -0/+21 |
| If there's an existing file foo when emitting a class file for foo.Bar, then emit an error at foo.Bar, similar to what javac does. The error message looks something like: foo.scala:4: error: error writing object Foo: ./mypkg/Foo.class: ./mypkg is not a directory | |||||
 |
index : scala | |
| The Scala programming language |
| summaryrefslogtreecommitdiff |