Re: [Boost-users] Limitations / Flaws with transformed_range

Subject: Re: [Boost-users] Limitations / Flaws with transformed_range
From: John M. Dlugosz (mpbecey7gu_at_[hidden])
Date: 2011-07-19 23:26:32

On 7/19/2011 6:10 PM, Nathan Ridge wrote:
>
>
> Looking at it again, it seems what you are really trying to do is write your own
> adaptor "ASCII_lowered" or something similar that would be used as
> "my_range | ASCII_lowered" (which is precisely what I was suggesting).

Right.

> As you discovered, returning transformed_range<ASCII_lower, const Range>
> won't work because src_prep() does not return "const Range", it returns
> something else.
>
> I see 3 solutions:
>

Updating the transformed_range constructor to take a template argument, as I showed, works 
perfectly, and is simpler than anything else.  That's why I suggest that this be applied 
to the Boost code.  Is there a way for a mere user to submit that formally?