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?
to your account
JavaConversions should be deprecated in favor of JavaConverters
The text was updated successfully, but these errors were encountered:
Imported From: https://issues.scala-lang.org/browse/SI-9684?orig=1
Sorry, something went wrong.
hey community — anybody want to put together a PR for this?
because why should soc have all the fun?
scala/scala#5064 and scala/docs.scala-lang#509
Previous work on the hardest problem in computer science: scala/scala@5d555ef
The naming convention didn't quite take. Was 2012 a long time ago or like yesterday? Git history, even when not squashed, seems to flatten all time.
Why can't we do this?
Quote of the day: "Initially motivated by #5580, then just motivated."
Doesn't typelevel.org offer a t-shirt that says, "Initially motivated by #2712, then just motivated."
Kieran Tully (kieran.tully-at-gmail.com) said:
You got there before me!
See also scala/scala#5065 for minor addition to your nice work.
Reassigning to M5. We'd probably want a change like this before the RC cycle starts.
Lukas suggested doc on the collection.convert._ members, which isn't done yet.
I'm happy to do the docs work, but i'd love to get some more opinions on my proposals on scala/scala#5064.
Successfully merging a pull request may close this issue.