News for hackers. Stuff that matters.
Re:Why I went from Python to Go (and not node.js) by jvm on Wednesday September 19, 2012 @10:07AM (#4543573)
Sorry to belabor the point, but this is exactly what parent was saying.

> changing something like > ("foo", > "bar", > "baz") > to > ("foo") > actually breaks the code.

Of course it breaks the code because the first thing is a tuple and the second is a string. He's implying that the second thing shouldn't be a string. I'm saying that's nuts.

Re:Why I went from Python to Go (and not node.js) by StavrosK on Friday September 21, 2012 @06:02AM (#4553080)
No, he's saying that the operation you perform to truncate the former to the latter is the operation you would logically expect to perform (i.e. removing the trailing comma), which makes the thing a string.

He's not actually proposing that a string be a tuple. He's just saying that a single element enclosed in parentheses doesn't work the way you'd expect it.

Re:Why I went from Python to Go (and not node.js) by achompas on Saturday September 22, 2012 @02:33PM (#4558593)
Thank you, Stavros.
Re:Why I went from Python to Go (and not node.js) by StavrosK on Saturday September 22, 2012 @06:38PM (#4559231)
You are quite welcome.