Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-06 Thread Nick Sabalausky
"Lars T. Kyllingstad" wrote in message news:hmnu5l$31j...@digitalmars.com... > > 3. It's sometimes unclear which symbols are members of a class/struct > and which are module-level symbols. Tango's API documentation is better > in this regard, since it has the symbol tree on the left-hand sid

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Jonathan M Davis
Jesse Phillips wrote: > Jonathan M Davis wrote: > >> Hmm. I'd thought that I'd looked at that one and determined that it >> didn't do what I was looking for, but on another inspection of it, it >> does look like until() will do the job. It has the potential downside >> that unlike find, it cannot

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Jesse Phillips
Jonathan M Davis wrote: > Hmm. I'd thought that I'd looked at that one and determined that it didn't > do what I was looking for, but on another inspection of it, it does look > like until() will do the job. It has the potential downside that unlike > find, it cannot take multiple ranges to be

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Philippe Sigaud
On Thu, Mar 4, 2010 at 13:12, Steven Schveighoffer wrote: > It is an issue with DDoc. I think the signatures are not that nasty if you > look at the actual code. I think DDoc expands all aliases so you get the > full template-expanded signature. > > The problem also is that when you use 'auto'

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Steven Schveighoffer
On Thu, 04 Mar 2010 03:55:40 -0500, Jonathan M Davis wrote: On a side note, it would be great if we could figure out a way to make the docs more user-friendly - especially in std.algorithm. The functions are great, and they're really versatile, but that seems to come at the cost of incred

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Lars T. Kyllingstad
Jonathan M Davis wrote: Lars T. Kyllingstad wrote: Jonathan M Davis wrote: std.algorithm.find() returns the rest of the range starting at what you were searching for (or an empty range if it wasn't in the given range). Is there a function in phobos which does a find but returns everything _bef

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Jonathan M Davis
Lars T. Kyllingstad wrote: > Jonathan M Davis wrote: >> std.algorithm.find() returns the rest of the range starting at what you >> were searching for (or an empty range if it wasn't in the given range). >> Is there a function in phobos which does a find but returns everything >> _before_ what you'

Re: D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Lars T. Kyllingstad
Jonathan M Davis wrote: std.algorithm.find() returns the rest of the range starting at what you were searching for (or an empty range if it wasn't in the given range). Is there a function in phobos which does a find but returns everything _before_ what you're searching for? I can't find one

D2: std.algorithm.find, but get part before what you were searching for

2010-03-04 Thread Jonathan M Davis
std.algorithm.find() returns the rest of the range starting at what you were searching for (or an empty range if it wasn't in the given range). Is there a function in phobos which does a find but returns everything _before_ what you're searching for? I can't find one that will do that, and I d