id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
2611	Unordered containers not usable when EBO is not supported	Andrey Semashev	Ion Gaztañaga	"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)."	Bugs	closed	Boost 1.45.0	intrusive	Boost 1.37.0	Problem	fixed	EBO intrusive stateless