summaryrefslogtreecommitdiff
path: root/.mailmap
diff options
context:
space:
mode:
authorJason Zaugg <jzaugg@gmail.com>2013-08-19 10:23:11 +0200
committerJason Zaugg <jzaugg@gmail.com>2013-08-19 10:36:44 +0200
commit6634d82f74b71dd36ca1ecceea08b4ad79335da0 (patch)
tree91c1603918f24bd3075e2bda155cc6d4c85e6431 /.mailmap
parent5084b74048f7f21f38fdf45ebfa8e634b863bb01 (diff)
downloadscala-6634d82f74b71dd36ca1ecceea08b4ad79335da0.tar.gz
scala-6634d82f74b71dd36ca1ecceea08b4ad79335da0.tar.bz2
scala-6634d82f74b71dd36ca1ecceea08b4ad79335da0.zip
SI-1980 A lint warning for by-name parameters in right assoc methods
The desugaring of right associative calls happens in the parser. This eagerly evaluates the arguments (to preserve left-to-right evaluation order the arguments are evaluated before the qualifier). This is pretty surprising if the method being called has a by-name parameter in the first parameter section. This commit adds a warning under -Xlint when defining such a method. The relevent spec snippets: > SLS 4.6.1 says that call-by-name argument "is not evaluated at the point of function application, but instead is evaluated at each use within the function". > > But 6.12.3 offers: > "If op is right- associative, the same operation is interpreted as { val x=e1; e2.op(x ) }, where x is a fresh name."
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions