Does it make sense to add goroutine / thread safe data structures for all the existing data structures? #215
Labels
No labels
bug
discussion
documentation
duplicate
ignore
new feature
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
golibs/gms-gods#215
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For example
concurrenthashset.go,concurrentpriorityqueue.go?Please let me know if this is a valid use case for majority of the people who are using this library in production, I am willing to contribute.
Related issue(s) : #68
Initially I intended to keep thread-safety and concurrency outside of this repo, but nowadays I think it makes sense to start introducing those structures