Waffle Maybe

@Yatekii how would it work though? `log_level` is defined as a [`log::Level`](https://docs.rs/log/0.4.17/log/enum.Level.html) (not optional) which can't ever be "off". : https://github.com/probe-rs/cargo-embed/blob/050a121dd1f66d9d097686cc2d4512e5e539220d/src/config/mod.rs#L70 Config is also merged with `default.toml`: https://github.com/probe-rs/cargo-embed/blob/050a121dd1f66d9d097686cc2d4512e5e539220d/src/config/mod.rs#L107 ... which...

I don't think that checking formatting is the way to go. A more interesting approach it to just make the formatting always correct -- either by creating the message with...

Hm, I see, the use-case of checking (template) messages beforehand is interesting. I'm not sure if it is or isn't in scope of `teloxide`, so I'll leave this issue as-if...

@Hirrolot I don't have any strong opinions on this. With subcommands there is a downside that auto-completion does not work anymore, meaning that say `/pr create` is a lot harder...

@rustbot label +T-libs-api -T-libs

Yeah, I think it's a good idea

Opened ACP: https://github.com/rust-lang/libs-team/issues/126

There are also `--test-builder`/`--runtool` unstable flags that are [used by miri](https://github.com/rust-lang/miri/pull/1757) to run doc tests

Hm, though the same problem occurs with `static/`... Maybe I don't understand what `get_url` is supposed to do?..

@mraerino I don't think this would work. If subcommand doesn't match (i.e.: default should be used) then your code will lose all arguments.