• Jonathan M Davis (9/9) Feb 19 2011 With the most recent release, we got findSplit, findSplitBefore, and fin...
• Tomek =?ISO-8859-2?B?U293afFza2k=?= (5/7) Feb 20 2011 Until is lazy, findSplit* are not.
• Andrei Alexandrescu (3/12) Feb 20 2011 until is lazy, findSplit* are eager.

Jonathan M Davis <jmdavisProg gmx.com> writes:

With the most recent release, we got findSplit, findSplitBefore, and
findSplitAfter 
in std.algorithm, which are all very useful and cool. However, in light of what 
they can do, I'm wondering if we really need std.algorithm.until? It seems to
me 
that the findSplit* functions give you that functionality, and I see no reason
to 
keep until around long term if it's not really giving us something that the 
findSplit* functions aren't.

Does anyone have a good reason why the findSplit* functions don't make until 
obsolete and unnecessary?

- Jonathan M Davis

Tomek =?ISO-8859-2?B?U293afFza2k=?= <just ask.me> writes:

Jonathan M Davis napisa=B3:

 Does anyone have a good reason why the findSplit* functions don't make un=

til=20
 obsolete and unnecessary?

Until is lazy, findSplit* are not.

--=20
Tomek

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 2/20/11 12:20 AM, Jonathan M Davis wrote:
 With the most recent release, we got findSplit, findSplitBefore, and
findSplitAfter
 in std.algorithm, which are all very useful and cool. However, in light of what
 they can do, I'm wondering if we really need std.algorithm.until? It seems to
me
 that the findSplit* functions give you that functionality, and I see no reason
to
 keep until around long term if it's not really giving us something that the
 findSplit* functions aren't.

 Does anyone have a good reason why the findSplit* functions don't make until
 obsolete and unnecessary?

 - Jonathan M Davis

until is lazy, findSplit* are eager.

Andrei