2 ms·
Not according to their blog post yesterday. They were absolutely defending it as the only consistent and reasonable choice
by 3836293648 4y ago
Not according to their blog post yesterday. They were absolutely defending it as the only consistent and reasonable choice
- Ygg2 4y agoWhat? 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.