Lonami

Something that's just as important is reviewing the errors that are exposed through the public interface. For this, it might be a good idea to pretend we're a user of...

The new-type pattern should probably be used for all the iterators, so that they can be exposed from the `grammers_client::client` module. The methods in the `Client` struct would then point...

[Future proofing](https://rust-lang.github.io/api-guidelines/future-proofing.html) should be taken into consideration.

Perhaps taking `AsRef` would enable people to send requests from things like `Box`, needs testing.

I don't need it, but someone might. Just like `std::fs` APIs take an `AsRef`, it might be a good idea to do something similar for more flexibility.

It's just changing `fn invoke(&self, request: &R)` for `fn invoke(&self, request: R)`. Why are you so opposed to it?

I'm still not sure how I'd like to design dealing with entities and access hashes in the library. The most likely problem here is that Telegram simply doesn't bother to...

Telegram rules are a bit weird. In theory, you need the `id` and `access_hash` for some "entity" (user or channel) to be able to use it (like fetch more information)....

No problem for asking, the library is extremely young, so finding where people struggle is key to work on those rough edges. Dialogs are fetched with [`messages::GetDialogs`](https://docs.rs/grammers-tl-types/0.2.0/grammers_tl_types/functions/messages/struct.GetDialogs.html). grammers needs to...

Not until friendly methods for them are made. You need to use `InputPeerEmpty` as the first offset.