-
Notifications
You must be signed in to change notification settings - Fork 87
Support all breaking changes listed in the FAQ #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone
Comments
-val xs: List[Int] = ys.map(f)(collection.breakOut)
+val xs = ys.view.map(f).to(List) map.zip(iterable)
map.zip(iterable).toMap -xs + 1 - 2
+xs ++ Set(1) -- Set(2) -xs.to[List]
+xs.to(List) -Set(1) + (2, 3)
+Set(1) + 2 + 3 -mutable.Set(1) + 2
+mutable.Set(1).clone() += 2 -mutable.Map(1 -> 2).updated(1, 3)
+mutable.Map(1 -> 2).clone() += 1 -> 3 -kvs.mapValues(f)
+kvs.mapValues(f).toMap -xs1.sameElements(xs2)
+xs1.iterator.sameElements(xs2) LinearSeq(1, 2, 3)
List(1, 2, 3)
|
@MasseGuillaume Following up on the discussion in #58 and #62, I suggest that we put aside these two items for now and we move forward to the next steps. What do you think? |
I’m closing this issue because we already have a specific issue for |
martijnhoekstra
pushed a commit
to martijnhoekstra/scala-collection-compat
that referenced
this issue
Nov 9, 2022
Add in-place shift operations to mutable.BitSet
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See: https://github.com/scala/collection-strawman/wiki/FAQ#what-are-the-breaking-changes
There are still some breaking changes for which we don’t have a migration rule.
The text was updated successfully, but these errors were encountered: