diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2014-01-07 14:01:24 +0100 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2014-01-07 15:53:45 +0100 |
commit | 5b9966d077b8fa7af95fa95d7782243892e6ccad (patch) | |
tree | bcc8bc2ca8252a5e1c13f06876623e7c9dd97664 /test/files/run | |
parent | 66a12fc264cae53107fda4feb5e42fda6879c1ae (diff) | |
download | scala-5b9966d077b8fa7af95fa95d7782243892e6ccad.tar.gz scala-5b9966d077b8fa7af95fa95d7782243892e6ccad.tar.bz2 scala-5b9966d077b8fa7af95fa95d7782243892e6ccad.zip |
SI-8120 Avoid tree sharing when typechecking patmat anon functions
When typechecking an empty selector `Match` corresponding to:
{ case ... => ... }: (A => B)
We wrap it in a `Function` and typecheck:
(x$1 => x$1 match { case ... => ... })
Local symbols in this expression (representing values bound by
the pattern, or just definitions in the body or guard) are then
owned by the anonymous function's symbol.
However, if we ever discard this `Function` and start anew with
the empty selector match, as happens during the fallback to
use a view on the receiver in `tryTypedApply`, we found that we
had mutated the cases of the original tree, and allowed orphaned
local symbols to escape into the compiler pipeline.
This commit uses duplicated trees for the the cases in the synthetic
`Match` to avoid this problem.
`duplicateAndKeepPositions` is used to preserve range positions;
without this scala-refactoring PrettyPrinterTest fails.
`Tree#duplicate` uses offset positions in the copied tree, which
is appropriate when both the original and the copy are going to end up
in the final tree.
Diffstat (limited to 'test/files/run')
0 files changed, 0 insertions, 0 deletions