Closed gaydenko closed 9 years ago
Aha, this issue comes from the fact that we have one codebase which we cross-compile for both Scala 2.10 and 2.11 (rather than maintaining separate branches for different Scala versions).
The good news is that this is a deprecation warning for us to deal with (it's between users of the macro/compiler API, not end-users) and is nothing for you to have to worry about.
It takes us going through and resolving all 2.10/2.11 deprecation warnings, which we'll do for the 0.9.0 release.
@heathermiller , OK, I see. Also the methods blow up scala-ide brain: http://gaydenko.com/tmp/su01.png Is it scala-ide issue?
Is there an alternative way of pickling/unpickling that doesn't yield this deprecation warning? I'm in the middle of transition to 2.11.1 myself so am compiling with "-deprecation" until I get all my code converted... So in the interim I can't use pickle which was one of the reasons for me to upgrade to 2.11.1...
Thanks
I don't think this happens with Pickling 0.10.0 + Scala 2.11.x any more.
Hi!
I have tried scala-pickling under 2.11.1 and have got deprecation warnings
against
pickle
andunpickle
methods. Not sure where to find this message de-cyphering for "normal users".How to resolve the deprecation?