Revised RFC on range design for D2

[Bill Baxter]

On Sat, Sep 13, 2008 at 5:11 AM, Andrei Alexandrescu
<SeeWebsiteForEmail at erdani.org> wrote:
> Walter Bright wrote:
>>
>> Andrei Alexandrescu wrote:
>>>
>>> Thanks. One problem in coding with first and last was that sometimes the
>>> code looks unnatural, especially when your range exposes a few more
>>> functions. In a stream parser, dealing with the "first" element is not the
>>> most natural way to think of it. But I agree that first and last are
>>> definitely palatable and natural most of the time. But then again, shouldn't
>>> any design have the inevitable cutesy that makes it memorable? :o)
>>
>> One consideration when selecting names is how it would interact with
>> google. One advantage to head/toe is there is already head/tail when
>> thinking of a list, and head/toe would fit into that naturally.
>
> I agree. Sorry tipsters. I think head/toe has one established thing and one
> cutesy. Tip/toe has two cutesies. An unwritten (or perhaps actually written)
> rule of good humor is that you shouldn't make a double pun. They somehow
> don't add to double effect.
>
> Andrei
>

Head / foot!

No cutesie == even better!

--bb