| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Make normalizeToRef survive annotated types | Martin Odersky | 2015-05-21 | 1 | -1/+1 |
| | | | | | Did not handle this case before. | ||||
| * | Disallow {...} arguments for annotations | Martin Odersky | 2015-05-21 | 1 | -0/+13 |
| | | | | | | This mimics scalac's behavior (but not the official syntax; in fact the official syntax seems to be ambiguous. | ||||
| * | Fixed test | Martin Odersky | 2014-12-19 | 1 | -3/+1 |
| | | |||||
| * | Allow for varargs passed to Java annotation constructors. | Martin Odersky | 2014-12-19 | 1 | -3/+5 |
| | | |||||
| * | Java annotations parsing problem | Dmitry Petrashko | 2014-11-22 | 1 | -1/+5 |
| | | | | | | | | | | | Annotations in java could be compiled as-if array-only annotation had <repeated> arguments constructor. That isn't true for scala. Also, type checking creation of single-element array requires implicit resolution to provide ClassTag. This makes problems while reading deferred annotation. | ||||
| * | Add the right constructor to Java annotations | Martin Odersky | 2014-11-22 | 1 | -0/+11 |
 |
index : dotty | |
| Research platform for new language concepts and compiler technologies for Scala. |
| aboutsummaryrefslogtreecommitdiff |