4 ms·

Say that to ?const ?async. If the keyword generics group doesn't accept that they're wrong they've killed Rust.

• zozbot234 4y ago
  ?const ?async is placeholder syntax. They'll bikeshed something better while stabilizing the language feature, much like the existing .await syntax which was chosen very late in development of async.
  • 3836293648 4y ago
    Not according to their blog post yesterday. They were absolutely defending it as the only consistent and reasonable choice
    • Ygg2 4y ago
      What? Where did you get that idea? I talked with them on Zulip, they were perfectly reasonable. Even on Reddit they consider alternative syntax like `print<?async, ?const>`. Issue is. They want code generation to solve coloring problem of async. I asked about using `#[maybe(async)]` syntax but they pointed that attribute macros have deficiencies. Can't differentiate on async-ness or lack of it, plus attribute macros lack exhaustiveness check that `match expr` afford.
• Ygg2 4y ago
  And community reacted unanimously against it. If they proceed blindly with it, then yes you will have a point.