-
Notifications
You must be signed in to change notification settings - Fork 1k
Corrected tuple definition #1728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Earlier statement was more ambiguous for a beginner.
I don't see how this is an improvement. Perhaps we can find some other way to improve it. What was the issue here that you saw? |
@SethTisue I feel the definition is bit ambiguous for a newcomer. The current definition somehow gives an impression that scala tupple only accepts distinct data type. It would be better if we add |
The problem I have with "same or distinct" is that in the overwhelming majority of cases, the types will be different. The case where all the types happen to be the same isn't common at all. Whereas phrasing it as "same or distinct" gives the impression that "same" is normal and expected, and that "distinct" is the alternative. |
Even though the majority use case will be for distinct types, I somehow feels documentation should be comprehensive. If you want, we can make it as |
I don't think "distinct or same" is clear, idiomatic English. It muddies the question rather than clarifying it. Maybe some entirely different phrasing such as "each with its own type"? |
How about this.
Or we could remove the phrase all together to avoid ambiguity.
|
The fact that the elements have individual types is one of the most crucial, important pieces of information on the entire page. Omitting it wouldn't make sense. "Homogeneous" and "heterogeneous" are big, obscure words — I don't think they improve the clarity. |
I have one more idea: replace "each with a distinct type" with "each with its own type"? |
I was referring this document for using these keywords. And same also needs to be updated i believe with the keyword "homogeneous". |
I don't like it there either :-) |
I went with "each with its own type" in 70a1166 |
Earlier statement was more ambiguous for a beginner.