This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: std::map and std::set based on AVL, not RB trees.
Gabriel Dos Reis wrote:
>Now, a question I raised earlier: when the standard is changed, the
>complexity will vanish?
>
>
When the Standard is *really* changed, this means that the LWG, having
considered all the various trade-offs, consider the new behavior an
improvement wrt the previous one. And we are going to implement it,
*definitely*.
In the meanwhile, is a change of behavior, not supported by an official
decision of the LWG, which has disadvantages, such as the "famous"
complexity and leads to surprises.
Paolo.
- References:
- std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.
- Re: std::map and std::set based on AVL, not RB trees.