Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Cull extraneous whitespace. | Paul Phillips | 2013-09-18 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | One last flurry with the broom before I leave you slobs to code in your own filth. Eliminated all the trailing whitespace I could manage, with special prejudice reserved for the test cases which depended on the preservation of trailing whitespace. Was reminded I cannot figure out how to eliminate the trailing space on the "scala> " prompt in repl transcripts. At least reduced the number of such empty prompts by trimming transcript code on the way in. Routed ConsoleReporter's "printMessage" through a trailing whitespace stripping method which might help futureproof against the future of whitespace diseases. Deleted the up-to-40 lines of trailing whitespace found in various library files. It seems like only yesterday we performed whitespace surgery on the whole repo. Clearly it doesn't stick very well. I suggest it would work better to enforce a few requirements on the way in. | ||||
* | Begone t1737... | Hubert Plociniczak | 2011-11-02 | 1 | -1/+1 |
| | |||||
* | Renamed Application to App. | Martin Odersky | 2011-02-21 | 1 | -2/+2 |
| | |||||
* | closes #3619, #4141. | Adriaan Moors | 2011-01-26 | 1 | -0/+34 |
replaced the epic outer.outer.outer by something more robust that goes to the context corresponding to the enclosing class nextOuter determines which context is searched next for implicits (after `this`, which contributes `newImplicits` below) in most cases, it is simply the outer context if we're owned by a constructor, the actual current context and the conceptual context are different when it comes to scoping: the current conceptual scope is the context enclosing the blocks that represent the constructor body (TODO: why is there more than one such block in the outer chain?) review by odersky, extempore |