Re: [Boost-users] [MultiIndex] is ordered_non_unique stable?

Subject: Re: [Boost-users] [MultiIndex] is ordered_non_unique stable?
From: Joaquin M Lopez Munoz (joaquin_at_[hidden])
Date: 2013-01-20 07:32:41

John M. Dlugosz <mpbecey7gu <at> snkmail.com> writes:

>     
> > The only problem with this is that the behavior is *undocmented*. If
> > you want to stay legal, use hinted insertion with end() (which will
> > *documentedly* work for all the ordered_non_unique indices of your
> > container, not only the one you happen to be doing for the insertion.)
>     
>     That is very interesting.  The wording is kind of strange though: 
>     "If succesful, insertion happens as close as possible to the
>     location just prior to position."Â  I wonder if
>     stability was the intention?

Well, the "inserted as close as possible to the position just prior to" the
hint policy is the exact wording in the standard, and Boost.MultiIndex just
follows suit.

Joaquín M López Muñoz
Telefónica Digital