You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 8, 2024. It is now read-only.
That was an oversight. In fact it looks like I actually neglected to call it ever, not just those two methods. Is there something special about those two?
Either way I think the right thing will be to call it in every method that calls GetKeysIterator. That's kind of annoying but I think it's the right behavior.
The other callers don't have any early returns and also don't have any abrupt completions (except for IteratorStep and IteratorValue, which are ignored for IteratorClose).
Set.prototype.isSupersetOf and Set.prototype.isDisjointFrom don't call IteratorClose, but instead directly return after calling SetDataHas. If this is intentional, it should probably be explicitly noted.
The text was updated successfully, but these errors were encountered: