diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2012-05-25 08:07:28 +0200 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2012-05-26 18:47:12 +0200 |
commit | 4794374af4d7c84ed6e06ac9c4e4f9f9d09cb102 (patch) | |
tree | d89f47528c5ed60970b4321aa0d6169a880a240a /test/files/run/syncchannel.scala | |
parent | 123050cf07229d02789dc42e27a85c93fd9343a4 (diff) | |
download | scala-4794374af4d7c84ed6e06ac9c4e4f9f9d09cb102.tar.gz scala-4794374af4d7c84ed6e06ac9c4e4f9f9d09cb102.tar.bz2 scala-4794374af4d7c84ed6e06ac9c4e4f9f9d09cb102.zip |
SI-5652 Mangle names of potentially public lambda lifted methods.
This can happen if they are accessed from an inner class. If a
subclass is happens to lift a public method to the same name,
a VerifyError ensues.
The enclosed tests:
- demonstrate the absense of the VerifyError
- show the names generated for the lifted methods (which are
unchanged if not called from an inner class, or if lifted
into a trait implementation class.)
- ensure that the callers are rewritten to call the correct
method when multiple with the same name are lifted.
It's not ideal that this phase needs a priori knowledge of the
later phases to perform this mangling. A better fix would defer
this until the point when the methods are publicised, and leave
the unmangled private method in place and install an public,
mangled forwarder.
Diffstat (limited to 'test/files/run/syncchannel.scala')
0 files changed, 0 insertions, 0 deletions