search for: convertiblerang

On Friday 15 May 2009 05:50, Jay Foad wrote: > > 3. Any comments on the patch itself? > > > > The one major thing to be aware of is that it isn't safe to use &V[0] > > when V is an empty std::vector > > Oh dear. That's a bit of a flaw in the plan. I suppose the solution is > to switch to SmallVector whenever this might be a problem. Or use iterators.

...e<std::basic_string<T,Ch,Alloc> > { enum { value = true }; }; template<typename T, bool True> struct type_if { typedef T type; } template<typename T> struct type_if<T,false> { /* cause substitution failure */ } // New prototype for ptr_range. template<typename ConvertibleRange> typename type_if< range<typename T::value_type*>, is_contiguous_sequence<T>::value >::type ptr_range(ConvertibleRange &seq); And secondly, range<T*> can be extended to convert from arrays in addition to objects with begin()/end() methods by (1) providing a...

> 3. Any comments on the patch itself? > > The one major thing to be aware of is that it isn't safe to use &V[0] when V > is an empty std::vector Oh dear. That's a bit of a flaw in the plan. I suppose the solution is to switch to SmallVector whenever this might be a problem. I'm a bit concerned that any new &empty[0] problems that are introduced will go unnoticed.