Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support STRICT_REPLACEMENT in ObjectLockingIndexedCollection/ConcurrentIndexedCollection #301

Open
npgall opened this issue Jul 25, 2022 · 0 comments
Assignees

Comments

@npgall
Copy link
Owner

npgall commented Jul 25, 2022

It would be beneficial if ConcurrentIndexedCollection and ObjectLockingIndexedCollection supported the STRICT_REPLACEMENT feature that is supported in TransactionalIndexedCollection.

The check would not be atomic/transactional in those collections. (In fact it would be susceptible to TOCTOU issues - which would need to be mentioned in documentation for those collections).

Rationale to do this, is that right now, the lack of this feature in all collections can cause different collections to behave differently when this feature is requested and not honoured by all collections, especially when multi-threading is not a factor. So implementing this feature will make the user experience more consistent.

@npgall npgall self-assigned this Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant