On Tue, 30 Mar 2010, Neil Groves wrote:
I suppose you should file a ticket, that's more useful than the list.
Which component should it be for? range or string_algo?
StringAlgo. The problem, of course, is that it's going to break some existing code.
If the patch was submitted in the middle of last year, do we need to make arrangements for someone to apply a fix in a shorter time frame? I'm quite happy to fix the defect regardless of which library requires modification, but I believe the required changes are in Boost.Algorithm and I would not want to cause any frustration.
What is going to happen with this on the release branch in particular? I will be merging over the BGL changes from the trunk and would like to know if the range algorithms will be in there (so I don't need to get them from boost/detail/algorithm.hpp). -- Jeremiah Willcock