Scala 2.13.16 release notes (DRAFT) #892
Conversation
2.13.16.md
Outdated
| * Deprecate `collection.mutable.AnyRefMap` ([#10862](https://github.com/scala/scala/pull/10862) by [@wangyum](https://github.com/wangyum)) | ||
| * It no longer has any performance advantage over `collection.mutable.HashMap` |
There was a problem hiding this comment.
"no longer" ... since when?
What is the recommendation for cross-compiling code, where Scala 2.12 performance still matters? (in my case, a lot, since it's linker code loaded through an sbt plugin)
Should we move to HashMap anyway, or should we ignore the deprecation with a compiler flag instead?
There was a problem hiding this comment.
since 2.13.0, as per https://github.com/scala/scala/releases/tag/v2.13.0 — I've pushed an edit to say so
for cross-compiling, I would suggest suppressing the deprecation warning, yes. (I mean if you really wanted you could use version-specific sources...)
There was a problem hiding this comment.
For those interested, here is the config we used to ignore those in bulk:
scalacOptions ++=
if (scalaVersion.value.startsWith("2.12.")) Nil
else Seq("-Wconf:cat=deprecation&origin=scala\\.collection\\.mutable\\.AnyRefMap.*:s")This reverts commit 35b11a5.
|
this is live now at https://github.com/scala/scala/releases/tag/v2.13.16 regardless, you can still give feedback on the notes, and suggest changes, here |
feedback welcome