Were multiple return values Go's biggest mistake?

Re:Were multiple return values Go's biggest mistake? by rat9988 on Saturday March 15, 2025 @02:58PM (#43374473)

> According to The Principle of Least Surprise (Principle of Least Astonishment, POLA)[1] there is should be a symmetry

I'm not sure you can say that. You might be the only one surprised by multiple inputs single output.

[ Parent | on HN ]

Re:Were multiple return values Go's biggest mistake? by nivertech on Saturday March 15, 2025 @03:01PM (#43374495)

What's more predictable: symmetry or assymetry?

Why there is so much symmetry in our world (Nature)?

[ Parent | on HN ]

Re:Were multiple return values Go's biggest mistake? by semiquaver on Saturday March 15, 2025 @03:15PM (#43374579)

I’m not sure what the name for this fallacy is. Appeal to unrelated concept?

Among the first functions children learn are things like addition of two numbers which lack this supposedly natural property.

[ Parent | on HN ]

Re:Were multiple return values Go's biggest mistake? by nivertech on Saturday March 15, 2025 @03:44PM (#43374750)

IMO you mistaken math-like infix notation with the number of arguments function receives.

  Tuple(Number,Number) -> add -> Number|Overflow

[ Parent | on HN ]

Re:Were multiple return values Go's biggest mistake? by rat9988 on Saturday March 15, 2025 @03:57PM (#43374816)

Depends how you imagine a function. Just imagine it like a funnel. Your argument is honestly at the very least irrelevant.

[ Parent | on HN ]