Ticket #2611 (closed Bugs: fixed)

Opened 8 years ago

Last modified 7 years ago

Unordered containers not usable when EBO is not supported

Reported by: andysem Owned by: igaztanaga
Milestone: Boost 1.45.0 Component: intrusive
Version: Boost 1.37.0 Severity: Problem
Keywords: EBO intrusive stateless Cc:


If EBO (Empty Base Optimization) is not supported by the compiler unordered containers cannot be used. That is, at least find functions don't compile because they internally use s_iterator_to on the slist bucket, which contains a check that its value_traits is stateless.

The root of the problem is in this check implementation and in the detail::is_empty_class implementation in particular. If EBO is not supported, the predicate will always return false.

I've encountered the problem with unordered containers, but I suspect other containers might be affected, too.

The proposed solution is to specialize is_empty_class template on the library-provided traits, so that it returns in the correct result. Or remove the stateless checks altogether. This should be noted in the docs (if the specialization approach is chosen, it should be said what template users have to specialize to make things work with their custom value traits).


Change History

comment:1 Changed 7 years ago by igaztanaga

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from Boost 1.38.0 to Boost-1.45.0

For compliant compilers now is_stateful_value_traits tries to detect that all needed functions are static.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.