+ 1
Tuple or no Tuple?
Why some people consider a bad practice return a Tupple in a method ?
2 Answers
+ 1
My guess would be because you already can return multiple variables with the out parameters or even references
+ 1
I believe it's the way tupples r currently used, it doesn't seem elegant seeing stuffs like tuple.item1 or tupples.item2 in code. I believe with C# 7 there will be a wider acceptability of tupples because the declaration n usage is now more readable and elegant