iterator __CLR_OR_THIS_CALL erase(const_iterator _First, const_iterator _Last)

iterator __CLR_OR_THIS_CALL erase(const_iterator _Where)

B>Что-то я навскидку не вижу преимуществ Метод собираемся вызывать неконстантный, значит под руками неконстантный контейнер, и получить неконстантные итераторы не составляет труда...

template<class charT,class traits,class Allocator>
inline typename std::basic_string<charT,traits,Allocator>::iterator
 erase(std::basic_string<charT,traits,Allocator>&                         s,
       typename std::basic_string<charT,traits,Allocator>::const_iterator first,
       typename std::basic_string<charT,traits,Allocator>::const_iterator last)
{
 assert(first<=last);

 assert(s.begin()<=first);
 assert(first<=s.end());

 assert(s.begin()<=last);
 assert(last<=s.end());

#if(__STL_BASIC_STRING_ERASE_USE_CONST_ITERATOR) //1 для STL из VS2008
 return s.erase(first,last);
#else
 return s.erase(s.begin()+(first-s.begin()),
                s.begin()+(last-s.begin()));
#endif
}//erase

КД>iterator __CLR_OR_THIS_CALL erase(const_iterator _First, const_iterator _Last)
КД>

КД>iterator __CLR_OR_THIS_CALL erase(const_iterator _Where)
КД>

КД>Надо будет такое в собственных контейнерах тоже реализовать

21.4.6.5/8 basic_string::erase
...
iterator erase(const_iterator first, const_iterator last);

It is the constness of the container which should control whether it can be modified through a member function such as erase(), not the constness of the iterators. The iterators only serve to give positioning information.

Here's a simple and typical example problem which is currently very difficult or impossible to solve without the change proposed below.

Wrap a standard container C in a class W which allows clients to find and read (but not modify) a subrange of (C.begin(), C.end()]. The only modification clients are allowed to make to elements in this subrange is to erase them from C through the use of a member function of W.
...
Proposed resolution:
...
Update the following signatures in 21.4.6.5 [string::erase]:
iterator erase(const_iterator const_position);
iterator erase(const_iterator first, const_iterator last);
...
The LWG believes that this issue should be considered as part of a general review of const issues for the next revision of the standard.