Re: [boost] Breaking existing libraries

If the compromise does not include going back to the old behavior for boost::iterator_range, then I'm open to suggestions

(Joke intended) This really doesn't seem to meet the criteria for a "compromise". Just sounds like you're getting your way.