Lonami
> This branch cannot be rebased due to conflicts Do you want to fix those or is merge OK?
My understanding of atomics was that this couldn't really happen, but that's clearly flawed. Since you seem able to reproduce the issue, would you mind attempting a fix and sending...
It hasn't been implemented fully. Maybe returning the `Message` is better / more obvious.
> the only way the state is handed is in-memory You can save the state to disk on demand: https://github.com/Lonami/grammers/blob/d180f024e553f05c6a5f120484ad68d2a2c5f73d/lib/grammers-client/examples/echo.rs#L97 My idea was that as soon as you got an...
> access hash maps But this should be fine. It only means the library may need to fetch more data to get it back, but that's it. I do not...
> What way does the application have to detect that a new chat was added to the chats map, without reimplementing the updates handling logic by itself None. But I'm...
> to persist the id and access hash in the database My thought was this would be done regardless for all incoming peers you could need, regardless of whether you...
[Another discussion about this](https://t.me/gramme_rs/29738) and brief reading of the linked docs made me realize that `grammers-session` likely does need to become both far more powerful and store both IDs *and*...
> include the peers database in the session? Yes. > introducing a `Storage` Yes, a [`trait` for `Session` is something we briefly discussed](https://t.me/gramme_rs/29747). Name bikesheddable, of course. > if we...