• H. S. Teoh (6/6) Apr 25 2012 Does std.regex support input ranges to match()? Or do I need to convert
• Dmitry Olshansky (11/13) Apr 25 2012 For now, yes you have to convert them. Any random access range of code
• MrSmith (3/16) Aug 11 2014 Is there any progress on this thing?

"H. S. Teoh" <hsteoh quickfur.ath.cx> writes:

Does std.regex support input ranges to match()? Or do I need to convert
to string first?

Thanks!


T

-- 
Tell me and I forget. Teach me and I remember. Involve me and I understand. --
Benjamin Franklin

Dmitry Olshansky <dmitry.olsh gmail.com> writes:

On 25.04.2012 23:08, H. S. Teoh wrote:
 Does std.regex support input ranges to match()? Or do I need to convert
 to string first?

For now, yes you have to convert them. Any random access range of code 
units should do the trick but stringish template constraints might kill 
that.

I plan to extend this eventually. The problematic point is that match 
internally is delimited by integer offsets (indices). Forward ranges 
technically can work (the match then will return something like 
take(..., n);) with a bunch of extra .save calls. Input ranges can't be 
used at all.



-- 
Dmitry Olshansky

"MrSmith" <mrsmith33 yandex.ru> writes:

On Wednesday, 25 April 2012 at 21:43:11 UTC, Dmitry Olshansky 
wrote:
 On 25.04.2012 23:08, H. S. Teoh wrote:
 Does std.regex support input ranges to match()? Or do I need 
 to convert
 to string first?

 For now, yes you have to convert them. Any random access range 
 of code units should do the trick but stringish template 
 constraints might kill that.

 I plan to extend this eventually. The problematic point is that 
 match internally is delimited by integer offsets (indices). 
 Forward ranges technically can work (the match then will return 
 something like take(..., n);) with a bunch of extra .save 
 calls. Input ranges can't be used at all.

Is there any progress on this thing?