Closed quake closed 2 years ago
I'm so sorry that I've been sitting on this, I'm finally coming back into open source work after a hiatus.
After thinking about this, I'm not sure I like the extra hash lookup in retain
or the fact that retain
now has to have an extra bound on Hash
and Eq
. I think I'd rather just document that retain
visits values in an arbitrary order. If it was truly needed, I would be more okay with adding a retain_ordered
method or something that has the extra ordered behavior. I don't think this is an obviously better implementation of retain
as it is, and I'd rather err on the side of obviousness.
@kyren I have updated pr according to your review comment, please review again, thanks.
resolve https://github.com/kyren/hashlink/issues/10