[Kwiver-announce] Best practices for passing inherited types through Sprokit Pipeline

[Matt Phillips]

Is the issue here just slicing when derived class objects are passed to
Keyframe selector?  I'm not familiar off the top of my head with how
sprokit does serialization/deserialization but might making that
'slice-proof' be the answer?  By e.g. storing type information and using
factory methods at construction.

Matt

On Wed, Nov 15, 2017 at 12:46 PM, Brian Clipp <brian.clipp at kitware.com>
wrote:

> Hi All.
>
> I ran into a case yesterday where I had a process that output a child
> class and a process that expected an input from it of the parent class.
> Sprokit's type checking fails in that case.  It lead me to spend some time
> thinking about what types to pass between processes.  After some discussion
> with Aaron and Matt B. these are some suggestions I've arrived at.
>
> Thoughts?
>
> Brian
>
> _______________________________________________
> Kwiver-announce mailing list
> Kwiver-announce at public.kitware.com
> http://public.kitware.com/mailman/listinfo/kwiver-announce
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/kwiver-announce/attachments/20171115/c3a40c7d/attachment.html>