yea, there's probably an argument that the comma is an overpowered part of the syntax given how small and similar to a period it is.
It's probably the buckling point for all the strains that the whitespace-as-syntax design creates.
Top-level
yea, there's probably an argument that the comma is an overpowered part of the syntax given how small and similar to a period it is. It's probably the buckling point for all the strains that the whitespace-as-syntax design creates. 2 comments
yea that's part of it, and all descending from the whitespace-as-syntax. My hot take would be that parens for literals (tuple or generator) should not be permitted as precedence/scope is too fundamental. If having `[]` and `{}` for literals feels inconsistent, then remove them too. tuple(), list(), set() and dict() are all right there and pretty pythonic IMO. If course, it's too late. But that comma being a little Paul Atreides of your code base is PITA. |
@maegul That, and the overload of () as precedence and tuple. Just got myself a tuple of two strings instead of a multi-line string ...