[Issue 10821] .byKey erroneously returns a null key

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sat Aug 17 13:17:55 PDT 2013


http://d.puremagic.com/issues/show_bug.cgi?id=10821



--- Comment #8 from hsteoh at quickfur.ath.cx 2013-08-17 13:17:55 PDT ---
It does not eliminate the bad behaviour though. Suppose you're iterating over a
RedBlackTree, and then add and delete some keys. Depending on whether those
keys are greater or less than the current key, they will be included / excluded
from the current iteration. So whether the key will be found in the current
iteration depends on the relative values of the current key and the key being
added/deleted, and there's no way to change this apart from scheduling
adds/deletes after the iteration is over.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list