15 Jun
2011
15 Jun
'11
10:23 a.m.
i have a reduced test case, which shows this behavior at [1] ... is this my fault (not using the unordered_set correctly) or is it a bug in boost.intrusive?
I think you forgot to include the link/attachment for '[1]'.
oops ... http://pastebin.com/KNXhuSiH
I don't know boost.intrusive very well, but you seem to be searching for the element rather than the key, is it possible that there's an implicit conversion from the element to the key, and you're searching on that?
i am inserting an element to the set, then i search for the element. i don't see how an implicit conversion could happen. thanks, tim