diff options
| author | Adriaan Moors <adriaan@lightbend.com> | 2017-02-26 16:01:37 -0800 |
|---|---|---|
| committer | Adriaan Moors <adriaan@lightbend.com> | 2017-02-27 17:15:43 -0800 |
| commit | 894b027ddf1551317ecdbda053aec90b6d6fa2f4 (patch) | |
| tree | 7191b771c3d19524f1eb4ef087c5cbfd35d79eaa /.mailmap | |
| parent | 011cc7ec86105640a6d606998f769986630fb62a (diff) | |
| download | scala-894b027ddf1551317ecdbda053aec90b6d6fa2f4.tar.gz scala-894b027ddf1551317ecdbda053aec90b6d6fa2f4.tar.bz2 scala-894b027ddf1551317ecdbda053aec90b6d6fa2f4.zip | |
Allow user-defined `[un]apply` in case companion
Don't emit a synthetic `apply` (or `unapply`) when it would
clash with an existing one. This allows e.g., a `private apply`,
along with a `case class` with a `private` constructor.
We have to retract the synthetic method in a pretty roundabout way,
as we need the other methods and the owner to be completed already.
Unless we have to complete the synthetic `apply` while completing
the user-defined one, this should not be a problem. If this does
happen, this implies there's a cycle in computing the user-defined
signature and the synthetic one, which is not allowed.
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions