Mindaugas Vinkelis

Yes... you're absolutely right, I cannot explain how it slipped. I just don't know how should I fix this. There are some nice improvements that deserve to be published in...

Hi, Variant serialization is straightforward. An example of how different variant types are handled is provided [here](https://github.com/fraillt/bitsery/blob/master/examples/composite_types.cpp). To serialize vector of variants you need to use lambda overload for `container`...

Hello, It's not ridiculous, but that would be a breaking change... and at the moment I don't want to introduce it without any additional value :) On the other hand,...

Serialization is very linear/serial process, especially for bitsery as it tries to save space for containers and there are some extensions as well. For this reason I guess you can...

Hello, There might be two things: First: ```cpp s.value4b(content_size); content.resize(content_size); for(uint i=0; i

This is implemented in v5.2.3.

Thanks for sharing! I'll leave this ticket open, so people would know about it.

@workingjubilee Thanks for your insights, it makes sense. I tried to implement lazy iterator, but it's not straightforward as it requires interior mutability. I noticed that we already have `From...

Summary of all changes so far: * provided new public function `BacktraceFrame::resolve(&mut self)` (this is the essence of the PR) * replaced `impl Into for Backtrace` with `impl From for...

Thanks for fast replay! but I really thing that `impl From for Vec` is not an issue. There's my reasoning. There's conversion only from Backtrace to BacktraceFrame: * both are...