Subject: [Boost-users] intrusive bug: equal_range implementation vs bounded_range precondition
From: Matei David (matei_at_[hidden])
Date: 2014-12-11 20:02:37
In the absence of a bug tracker, I'll post the potential bug here:
I'm seeing some strange results out of `multiset::equal_range`. I
didn't isolate a test case, but looking at the code something seems
wrong:
The `bstree_algorithms::equal_range(const KeyType &, KeyValueCompare)`
method is currently implemented (in `bstree_algorithms.hpp`) as a call
to `bstree_algorithms::bounded_range(header, key, key, comp, true,
true)`. However, `bounded_range` states as prerequisite: If 'lower_key'
== 'upper_key', ('left_closed' or 'right_closed') must be false.
Either the `equal_range` implementation or the `bounded_range`
precondition is wrong.
Matei