scala.collection.mutable.Stack deprecated #147
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Scala 2.12 produces warnings about deprecations, there are others, but this is a particular brutal one.
Convert uses of
mutable.Stack
toimmutable.List
andvar
.I've tried to preserve binary compatability, by creating members that use
collection.mutable.Stack.apply
, but I don't get the deprecation warnings. Must be only the constructor has deprecation warnings? Regardless, the changes to avoid mima complaining is fraudulent binary compatability: I created members of the type mima wants, but the values are not actually used. So if users dependended on these members in their code, this would break. I don't think this is very likely, because the code smells very much like internal accounting.Maybe we just change everything to
List
, break bincompat, add entries tomimaBinaryIssueFilters
and call it fixed instead?