nielsle

Some users will be confused that a postfix macro can change the control flow even though it looks like a method. This can lead to obfuscated code. I can imagine...

You can do this with `rust-enum-derive`. See `#[DeriveIterVariants(..)]` ``` custom_derive! { #[derive(Debug, PartialEq, Eq, IterVariants(CandyVariants))] pub enum Candy { Musk, FruitRock, BoPeeps, LemonSherbert } } ``` Links: - https://danielkeep.github.io/rust-custom-derive/doc/enum_derive/index.html -...

I am not a tokio developer, but tower-rs looks like a replacement for tokio-proto https://github.com/tower-rs/tower

It would be great to have the following optional notation ~~~ info!("..."; a, b); ~~~ This could men the same as ~~~ info!("..."; "a" => a, "b" => b); ~~~...

It looks like the original poster wanted to remove unused imports. You can use 'cargo machete' for this https://github.com/bnjbvr/cargo-machete

The [Const generics"-RFC](https://github.com/rust-lang/rfcs/pull/2000) will allow types that are generic over an integer parameter. This will probably be useful for defining ranged types in a library.

See also https://github.com/est31/cargo-udeps (untested)

I would personally prefer a single option to turn of all link previews in all posts. I don't need special settings for each author. Keep it simple :-)

I think that the RFC should mention #1672 and mutually exclusive traits https://github.com/rust-lang/rust/issues/20400 https://geo-ant.github.io/blog/2021/mutually-exclusive-traits-rust/ https://stackoverflow.com/questions/57749827/mutually-exclusive-traits Is this RFC an alternative to #1672 or is it orthogonal?

Also compare with #20188 "Option to disable external link previews". Perhaps the collapsed version of he post could show the link without the preview.