summaryrefslogtreecommitdiff
path: root/test/files/run/trait-default-specialize.check
Commit message (Collapse)AuthorAgeFilesLines
* Don't generate specialized overrides in traitsJason Zaugg2015-08-111-1/+0
| | | | | | | | | | | | | | The term "specialized override" is used to describe a method in a synthetic specialized subclass that generically substitutes the specialized type args into the siganture of a generic method. For example, `trait T[@spec A] { def t(a: A) }` gives rise to `def t(a: Int)` under the type environment `A=Int`. This commit avoids doing this for specialized traits, only classes have these overrides now. The motivation is to make it simpler to use specialized interfaces (like `T$mcI$sp` from the example above) as Java functional interfaces.
* Test case for the status quo in specialized traitsJason Zaugg2015-08-111-0/+4
A deferred method in the generic interface ends up with a corresponding, generically substituted version in the specialized sub interface. This is superfluous and problematic when we start adding default methods to the interfaces. The subsequent commit will remove them.