Tuples, C#, Java, language design

[grauzone]

justme wrote:
> grauzone Wrote:
> 
>> justme wrote:
>>> bearophile Wrote:
>>>
>>>> C# will probably not follow the route of stagnation of Java for some more time, thanks to Mono too. I don't like that string interpolation syntax because it looks unsafe, and that design of tuples can be improved, but they are listening to programmes (even if they risk creating a mudball language):
>>>> http://www.infoq.com/news/2009/12/Mono-CSharp-Ex
>>>>
>>>> More on those tuples:
>>>> http://tirania.org/blog/archive/2009/Dec-23.html
>>>>
>>>> Eventually it will be quite useful to have some very well designed multi-return support in D (like those tuples, but better).
>>> Doesn't D2 already have tuples in Phobos. D has the comma operator which C# doesn't so such syntax is not possible in D, me thinks.
>> But tuples in D really suck. Compared to other languages, D tuples feel 
>> inflexible, stiff, and complicated.
> 
> The burden of proving your claims is still there. Isn't D meritocracy - nobody listens your opinions unless you post compiler / stdlib patches. I believe the Phobos tuple classes are sufficient until a better system arrives in D3 or D4. D2 book is almost finished so you need to write your patches against D3 now.

My experience with patches is, that they're mostly either ignored or 
rejected. I guess the chance of an unrequested patch changing a core 
language feature in crucial ways is 200%. Walter doesn't listen to 
anyone anyway *g*.

The downsides of D tuples has been often mentioned, e.g. here: 
http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=98953
(Sorry, I'm not as eloquent as language_fan to write it up myself, plus 
nobody would read it.)