News for hackers. Stuff that matters.
Re:Why the C++ standard ships every three years by blt on Saturday July 13, 2019 @05:26PM (#20430261)
Special keywords like `fn` make parsing simpler. Trailing return types are useful in languages that support generic programming, because they make it easier to write a function whose return type depends on the types of its generic inputs. Even C++ has this feature now, using decltype and arrow notation:

    template<typename T, typename U>
    auto add(T t, U u) -> decltype(t + u)
    {
        return t + u;
    }
C++ is notoriously hard to parse. Consider the "most vexing parse", or the fact that refactoring tools for C++ are always flakier than their Java / C# / Go equivalents, or the fact that https://cdecl.org/ exists. New languages in the "expressive, high performance" niche cannot continue to be held back by C++ syntax.
Re:Why the C++ standard ships every three years by jimmaswell on Saturday July 13, 2019 @05:33PM (#20430299)
C# and Java as you mentioned use very C++-like syntax.
Re:Why the C++ standard ships every three years by joshuamorton on Saturday July 13, 2019 @07:02PM (#20430676)
To a first approximation, yes. But consider that the C++ grammar has ~100 more rules than Java (~170 vs. ~280), and parts of the C++ grammar are strongly context-dependent, which isn't true in Java.
Re:Why the C++ standard ships every three years by llukas on Saturday July 13, 2019 @06:36PM (#20430571)
Tools can use LLVM infrastructure to get ast. No need to parse it yourself.
Re:Why the C++ standard ships every three years by MauranKilom on Sunday July 14, 2019 @10:37AM (#20433627)
The AST is still really complex though (in terms of corner cases to cover).