Revised RFC on range design for D2

[Pablo Ripolles]

Andrei Alexandrescu Wrote:

> Bill Baxter wrote:
> > On Fri, Sep 12, 2008 at 11:39 PM, Andrei Alexandrescu
> > <SeeWebsiteForEmail at erdani.org> wrote:
> >> Pablo Ripolles wrote:
> >>> What about "isDone"?
> >> isDone is great, I just wanted to keep the one-word streak going. Let's see
> >> what everyone else says.
> > 
> > Hmm.  std.algorithm does have an "isSorted" function.  So I guess I
> > agree it would be more consistent if you call it isDone or isEmpty.
> > 
> > Or rename "isSorted" to "sorted".  :-)  But then you have to face the
> > consequences later when you want to have a predicate that is ambiguous
> > without the "is".    Probably a lot of noun predicates are in that
> > category -- i.e. checking  isSomeNoun(x).  Like "isRange(x)" to see if
> > x is a range.  That would have to just become "range(x)" which is a
> > bit ambiguous.
> > 
> > So I agree. Stick the "is" in there.
> 
> Thing is, people will call isSorted much less often than (isD|d)one. In 
> std.algorithm clearly the one-word paradigm can't scale. But for a 
> handful of heavily-used names I'd be willing to take the Pepsi challenge.
> 
> Andrei
> 
> P.S. The more I think of it, the more I like "tip" of the range. Short, 
> poignant, easy to remember. Not pressing the red button just yet.

A perhaps more aeronautical term but short and nice as an alternative to "tip" might be "aft".

So, what about "aft" instead of "tip"?

"head"/"aft" it's not that bad, is it?

Cheers!