3 ms·
A lot of people in this thread are using this to make fun of Python, but the exact same issue exists in something like c++, here's some I fixed recently: https
by ehsankia 5y ago
A lot of people in this thread are using this to make fun of Python, but the exact same issue exists in something like c++, here's some I fixed recently:
https://github.com/UWQuickstep/quickstep/pull/9 https://github.com/UWQuickstep/quickstep/pull/9
https://github.com/tensorflow/tensorflow/pull/51578 https://github.com/tensorflow/tensorflow/pull/51578
https://github.com/mono/mono/pull/21197 https://github.com/mono/mono/pull/21197
https://github.com/llvm/llvm-project/pull/335 https://github.com/llvm/llvm-project/pull/335
- aeturnum 5y agoI didn't understand anyone to be saying that Python is the only language to have this flaw. Also, I personally don't mind this approach to string concatenation. I think it's a fine compromise between easy formatting and clarity. I was whining about a corner case of tuple construction - which as far as I know is not a feature of any other language.
- rstuart4133 5y agoA better compromise is to insist on this: ( "one", ( "a very very" "long long two" ), "three" ) And of course a,b should be syntactically invalid. It must be (a,b)