Bartosz Sypytkowski

Generally speaking snapshots may not work correctly with with `Doc::new` as the default options have block garbage collection turned on. You need to turn on [skip_gc](https://docs.rs/yrs/latest/yrs/struct.Options.html#structfield.skip_gc) flag (`Doc::with_options(Options {skip_gc:true, ..Options::default()})`),...

@rbtying thanks for the error message, but can you provide more context? What code caused that issue and which version of yrs are you using?

@rbtying since 0.17.4 to current one (0.19) we've rewritten observer API twice. The code that is causing this panic doesn't exist for a long time.

Hi @SebastianStehle - re. node pointers: I'll be working on fixing the issue after the next release (v0.17). There's already quite a lot on a plate and I don't want...

That being said this feature can be messy on the receiving end. Assuming BranchPtr representations as `struct BranchPtr(u32)` we need to somehow cover situations where it refers to a node...

If we're about to change the API, I'd prefer to go all way through and implement 2nd approach - it's way more descriptive and reduces number of redundant checks: ```rust...

> The whole point of the indirection is to prevent non-catchable process faults. What I meant here was: ```rust // this code works as it used to - if ymap...

> 1. How are events cleared? Event's lifetime is guaranteed only for the duration of a callback and should never be done outside of it. This also covers accessing event...

> The problem is that it is really hard to catch these errors in .NET, so accessing an invalid pointer could crash the application and this can happen relatively easy....

Current way of working with that was to not hold on to references that you expect to get destroyed. Why? While it's semi possible to make things work on the...