Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Revised restrictions for value classes and unversal traits | Martin Odersky | 2012-10-03 | 1 | -2/+2 |
| | | | | | | | | | and brought compiler in line with them. One thing we can accept IMO are nested classes (nested objects are still a problem). In fact, it makes no sense to exclude nested classes from value classes but not from universal traits. A class nested in universal trait will becomes a class nested in a value class by inheritance. Note that the reflection library already contains a universal trait with a nested class (IndexedSeqLike), so we should accept them if we can. | ||||
* | Fixed test cases. | Martin Odersky | 2012-03-21 | 1 | -4/+1 |
| | |||||
* | Fixes to value classes: Flags now double definitions, private constructors ↵ | Martin Odersky | 2012-03-06 | 1 | -14/+17 |
| | | | | as errors. Fixed erasure scheme. | ||||
* | Compiler now ready to accept value classes in standard library. Time for a ↵ | Martin Odersky | 2012-02-22 | 1 | -4/+1 |
| | | | | new STARR! | ||||
* | Implemented super access in value classes, restrictions for value classes. | Martin Odersky | 2012-02-19 | 1 | -0/+46 |