Dmytro Polunin
Dmytro Polunin
Maybe macro will create namespaces with memory layout as name? e.g. `types::std140::Foo` and `types::packed::Foo`.
I think that we can add extension method `Bot::send_long_message()` which will split input text. Library users know where their messages can be long, so they can only use this method...
The wrapper must impl each method, so if we decide to create `SplitLongMessagesBot` wrapper, it must also implement each method. This will cause compile- and IDE perfomance decrease. Teloxide has...
What you mean when you say _deep-linking_? Links like `tg://user?id=12345678`?
It requires to use anything like `BotTrait`, yeah? It is interesting idea by her own. It will allow to create many different variants of `Bot` include `I18NBot` which we discussed...
We can add crutches like the macro attributes inside macro: ```rust #[derive(BotCommand)] enum Command { Foo, #[command(linear_args_separator = "my-separator")] Bar(LinearArgs) } ``` which expands into: ```rust impl BotCommand for Command...
Or we can just use the separator which defined at the enum level (whitespace by default, can be override by `#[command(separator = "my-separator")]` like [here](https://github.com/teloxide/teloxide/blob/dev/tests/command.rs#L126))
@Hirrolot I remember that studylearner do something similar
@berkus just now you can implement `BotCommand` for your `Command` enum by yourself.
This is not possible with current Rust - I've tried many different approaches and no one is working for `teloc`. There are two possible options: 1. We need new feature...