Comments (5)
Matthieu, I think this does what you want:
implicit def cPickler[T <: X] = new CustomPickler[T]
from pickling.
We don't have much for documentation (yet) of scala-pickling (besides an academic paper which covers some of these things, but is definitely not ideal for developers). Apologies– comprehensive documentation is on the way.
An important detail that you might not know is that SPickler[T]
is meant to pickle only objects of type T
, but not subtypes of T
.
That means that when you define:
implicit def cPickler = new CustomPickler[X]
A CustomPickler[X]
is introduced in the implicit scope, but CustomPickler
s for any of X
's subtypes are not introduced into implicit scope. So, @markehammons is correct– the easiest way, when supplying your own custom picklers, and dealing with subtypes, is to be explicit that your custom pickler is also suitable for subtypes of X
:
implicit def cPickler[T <: X] = new CustomPickler[T]
from pickling.
Could you let us know if this clarifies things/solves your problem?
from pickling.
It clarifies this point yes, thanks. I stay tuned for more documentation then !
from pickling.
Awesome- thanks, closing this then. :)
from pickling.
Related Issues (20)
- Improve performance of implicit search HOT 3
- StaticOnly should be enabled by default HOT 2
- Refined types should be supported HOT 1
- Cut first milestone release HOT 13
- Add picklers and unpickler for Nothing HOT 1
- Variadic arguments for case class HOT 4
- Remove patmat warnings HOT 1
- Can't unpickle ValueSet HOT 2
- Pickling 0.10.2-SNAPSHOT for Scala 2.10
- Compile time serialisation failing for nested case classes with Scala 2.10.6 HOT 2
- Error when saving a Map of Int and a Composite
- java.lang.VerifyError: Bad type on operand stack while encapsulating Pickler
- Some macro in PicklerUnpickler is not serializable
- Deserialization in incorrect type
- Consider dropping or updating the link to http://lampwww.epfl.ch/~hmiller/pickling
- Unpickle without specifying type HOT 1
- Is this project abandoned? HOT 14
- Incorrect handling of Option[xxx] if None HOT 13
- val from trait not pickled
- Pickling fails with a weird issue
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pickling.