July 09, 2015
On Thursday, 9 July 2015 at 00:48:40 UTC, Tofu Ninja wrote:
> Languages with something called a list that is indexable...
> Java
> C#
> Python
> Perl

Tcl (lists are an absolutely fundamental part of this language)
Lisp
Haskell
Icon
July 09, 2015
On Thursday, 9 July 2015 at 00:11:17 UTC, Walter Bright wrote:
> Which is why I simply picked the name Arguments. The s suffix means plural, and doesn't give any preconceived notion about what kind of collection it is. It's a convention I've been using in the dmd source for some time now, and have found it to be natural and pleasing.

Instead, it gives the idea that they're used specifically for arguments, which they aren't. They get used for a variety of things. Also, the term Arguments is going to be really confusing - just like talking about std.container.Array gets confusing, because the term array is already used for other stuff, and it's never clear what folks are talking about unless they get specific. At least when you use the term TypeTuple, everyone knows what you mean, even if it's a sucky name. Going with something like Arguments or Parameters or Aliases is just going to breed confusion.

- Jonathan M Davis
July 09, 2015
On 7/8/2015 7:22 PM, Jonathan M Davis wrote:
> On Thursday, 9 July 2015 at 00:11:17 UTC, Walter Bright wrote:
>> Which is why I simply picked the name Arguments. The s suffix means plural,
>> and doesn't give any preconceived notion about what kind of collection it is.
>> It's a convention I've been using in the dmd source for some time now, and
>> have found it to be natural and pleasing.
>
> Instead, it gives the idea that they're used specifically for arguments, which
> they aren't. They get used for a variety of things. Also, the term Arguments is
> going to be really confusing - just like talking about std.container.Array gets
> confusing, because the term array is already used for other stuff, and it's
> never clear what folks are talking about unless they get specific. At least when
> you use the term TypeTuple, everyone knows what you mean, even if it's a sucky
> name. Going with something like Arguments or Parameters or Aliases is just going
> to breed confusion.

What about the 's' suffix?

July 09, 2015
On Thursday, 9 July 2015 at 02:58:32 UTC, Walter Bright wrote:
> On 7/8/2015 7:22 PM, Jonathan M Davis wrote:
>> On Thursday, 9 July 2015 at 00:11:17 UTC, Walter Bright wrote:
>>> Which is why I simply picked the name Arguments. The s suffix means plural,
>>> and doesn't give any preconceived notion about what kind of collection it is.
>>> It's a convention I've been using in the dmd source for some time now, and
>>> have found it to be natural and pleasing.
>>
>> Instead, it gives the idea that they're used specifically for arguments, which
>> they aren't. They get used for a variety of things. Also, the term Arguments is
>> going to be really confusing - just like talking about std.container.Array gets
>> confusing, because the term array is already used for other stuff, and it's
>> never clear what folks are talking about unless they get specific. At least when
>> you use the term TypeTuple, everyone knows what you mean, even if it's a sucky
>> name. Going with something like Arguments or Parameters or Aliases is just going
>> to breed confusion.
>
> What about the 's' suffix?

It might work in a situation where the main word is clearly unique, but when you're talking about something like Argument or Alias, adding an s on the end does not help at all. It's far too easy to confuse it with other concepts in the language that have the same name, whereas putting something like List on the end wouldn't have that problem - e.g. no one is going to confuse AliasList for anything else, but if we had Aliases, it would be really easy to think that someone was referring to aliases like this

alias foo = bar;

and misunderstand what they were talking about - especially in verbal conversations.

- Jonathan M Davis
July 09, 2015
On Thursday, 9 July 2015 at 03:31:41 UTC, Jonathan M Davis wrote:
>
> alias foo = bar;
>
> and misunderstand what they were talking about - especially in verbal conversations.
>
> - Jonathan M Davis

Maybe with time, people will learn to use d:s module system verbally and say things like " meta pack" when referring to meta.Pack etc.
July 09, 2015
On Thursday, 9 July 2015 at 00:11:17 UTC, Walter Bright wrote:
>
> Which is why I simply picked the name Arguments. The s suffix means plural, and doesn't give any preconceived notion about what kind of collection it is. It's a convention I've been using in the dmd source for some time now, and have found it to be natural and pleasing.

+1

--
Paolo


July 09, 2015
On Thursday, 9 July 2015 at 01:26:57 UTC, Observer wrote:
> On Thursday, 9 July 2015 at 00:48:40 UTC, Tofu Ninja wrote:
>> Languages with something called a list that is indexable...
>> Java
>> C#
>> Python
>> Perl
>
> Tcl (lists are an absolutely fundamental part of this language)
> Lisp
> Haskell
> Icon

Several of which actually use linked list for list and probably shouldn't provide random access.
July 09, 2015
On Thursday, 9 July 2015 at 02:58:32 UTC, Walter Bright wrote:
> What about the 's' suffix?

I use it for collection names quite a lot. Like:

Foo[] foos;

But I wouldn't go for

alias Foos = Foo[];

Additionally, we have this language concept that is autounpacking and so on and have no name. It needs a name.

This construct does not exists in most languages, so we need to come up with a name.

July 09, 2015
On Wednesday, 8 July 2015 at 18:01:36 UTC, Steven Schveighoffer wrote:
> On 7/8/15 1:44 PM, Timon Gehr wrote:
>> On 07/08/2015 11:38 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?=
>> <schuetzm@gmx.net>" wrote:
>>>
>>>
>>> I like "AliasTuple" as suggested by Martin, although it isn't a perfect
>>> fit either when you think of `alias` template params, which don't match
>>> `int`, while `int` can be an element of a TypeTuple.
>>
>> But this works: alias Int = int;
>>
>> The right fix for this issue is to fix the language. This does not make
>> any sense.

Of course, but I thought that was out of question. However...

>
> Yes, Walter at dconf also (I think) agreed this at least needs to be fixed:

... that's nice to hear!

Then I think we should definitely go with "AliasTuple".
July 09, 2015
On Thursday, 9 July 2015 at 08:03:06 UTC, deadalnix wrote:
[..]
> Additionally, we have this language concept that is autounpacking and so on and have no name. It needs a name.
>
[..]

Unrolling    ?