diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2013-11-24 21:34:57 +0100 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2013-11-24 21:42:06 +0100 |
commit | 2ce7b1269aebcc83ee433f4114779e54ee43f9f3 (patch) | |
tree | 012b34450f515681f5a01c870afa0d001990fac8 /test/files/pos/t4365 | |
parent | c243435f113615b2f7407fbd683c93ec16c73749 (diff) | |
download | scala-2ce7b1269aebcc83ee433f4114779e54ee43f9f3.tar.gz scala-2ce7b1269aebcc83ee433f4114779e54ee43f9f3.tar.bz2 scala-2ce7b1269aebcc83ee433f4114779e54ee43f9f3.zip |
Deprecates Par*View and Gen*View
In 2.12, this gives us the option to move the code from
Gen*View down into *View. If we don't do something more
drastic with views, which inertia and history suggests
is a real possibility, we can at least shed a little of
the implementation.
These abstractions are *only* used to share implementation;
there is no `view` method available on, for instance, `GenSeq`
that lets one abstract over parallel/sequential collections
while spawning views.
scala> (List(1): collection.GenSeq[Int]).view
<console>:8: error: value view is not a member of scala.collection.GenSeq[Int]
(List(1): collection.GenSeq[Int]).view
^
Let's keep it that way.
I suspect that views over parallel collections exist not because
they were the most sought after feature, but rather because the
initial incarnatin of parallel collections used to live undernead
TraversableOnce, and hence were obligated to implement `def view`.
This change will give us deprecation warnings in the non deprecated
places that extend `Gen*View` (three, by my count) in the interim.
There are ways to avoid this, but they aren't particularly appealing.
Diffstat (limited to 'test/files/pos/t4365')
0 files changed, 0 insertions, 0 deletions