LasterAlex
LasterAlex
> You can add syntax sugar of this kind in the current PR, if it won't bring too much hassle to you. Awesome! Will do, it won't take much
> To be clear, we decided to deal only with one request at a time, right? Yes, it's quite hard to implement a sane solution without panics or recreating setters...
Awesome! Very glad to do it!
Yup, I thought bot adaptors used `deref`, but no, thanks for pointing it out! You can use the #1213 branch until it's merged
Hm, maybe it's also good to make something like `.enter_dialogue_or(async |u: Update| {...})`? For the ability to say "Sorry, bot updated, resetting your state..." or smth?
Needed to add Clone restriction
Nope, but I don't see a way around it Also, why is calling `Default` twice bad?
Oh... Yeeeeeeeeah, thanks telegram Well, then... Creating a separate enum could be a solution, but it will be off-standard Or maybe add a check in send_media_group that the item doesn't...
I tried to play around with proc macros to no avail, so i see as a solution only two options: 1. Panic if you pass in InputMedia::Animation (bad because no...
Well, yeah, an additional type is a good guarantee, and yes, it will be useful if telegram decides to add a new exception Maybe it is the way And now...