And yes, these proposed syntaxes for Rust are not practical because Rust's support for macro definitions relies on the existing syntax. But if you're willing to reimplement any macros, it becomes viable.
X!(T)
X!T
are the same. This was Andrei's idea, and it worked out nicely.I suppose that dates back to my aviation experience, where if an airplane is beautiful it very likely flies well, too.
https://github.com/rust-lang/rfcs/pull/3267
I was against because I felt that there should always be parens/brackets/braces (macros can use any of them) for better scannability when you're invoking an unclear amount of extra stuff behind the scenes.
(An appeal to the "make costs explicit" side of Rust's philosophy that also requires explicit .clone() rather than copy constructors.)
Here's the summary of why the consensus was "no":
https://github.com/rust-lang/rfcs/pull/3267#issuecomment-128...