diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2013-06-16 14:15:30 -0400 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2013-06-16 17:09:33 -0400 |
commit | 83ae74ce9d3ff56c47b39e44332daa3da2981133 (patch) | |
tree | 2dfcbdad1ecb2039fe606730f348c2bdb2267d19 /test/files/neg/t6728.scala | |
parent | 70a93f52c3efafe604d6547b335cc361deff4f29 (diff) | |
download | scala-83ae74ce9d3ff56c47b39e44332daa3da2981133.tar.gz scala-83ae74ce9d3ff56c47b39e44332daa3da2981133.tar.bz2 scala-83ae74ce9d3ff56c47b39e44332daa3da2981133.zip |
SI-7584 Fix typer regression with by-name parameter types
It regressed in fada1ef6b#L4L614. Partially reverting just
this change restores the correct behaviour:
```
- if (sym.isStable && pre.isStable && !isByNameParamType(tree.tpe) &&
+ if (treeInfo.admitsTypeSelection(tree) &&
```
This patch embeds the check for by-name parameter types into
`TreeInfo.isStableIdentifier`. That code already checks for
`Symbol#isStable`, which exludes direct references to by-name
parameters. But the additional check is required to deal with
by-name parameters in function types, e.g `(=> Int) => Any`.
Open question: should we go further and embed this check in `isStable`?
Currently:
final def isStable = isTerm && !isMutable && !(hasFlag(BYNAMEPARAM)) && (!isMethod || hasStableFlag)
Such function types are an underspecified corner of the language,
albeit one that is pretty useful writing, for example, in the
signature of a lazy foldRight that can operate over infinite
structures:
def foldRight[A, B](fa: F[A], z: => B)(f: (A, => B) => B): B
The next commit subjects them to a little testing.
Diffstat (limited to 'test/files/neg/t6728.scala')
0 files changed, 0 insertions, 0 deletions