Re: RFC: short and inner classes

On 14/03/2025 21:18, Bilge wrote:

Just because some (incompetent) developers cannot grasp proper escaping should have no bearing whatsoever on language design.

The main problem is not "grasping" it, it's the inconvenience of having to do it at all, and the "ugliness" (subjective, obviously) of the resulting code. Backslash is used as an escape in so many different syntaxes that it's not uncommon to be nesting two of them inside each other, e.g. Markdown inside JSON: { "markdown": "The inner class is called MyNamespace\\\\MyClass\\\\\\\\InnerClass" } The quadrupled namespace separator is still just about readable, but could you tell me at a glance if I have the right number of backslashes for the proposed inner class separator? If we can't use "::", I'm confident we can find one that's more convenient to use than double-backslash. -- Rowan Tommins [IMSoP]