Does it make sense to add goroutine / thread safe data structures for all the existing data structures? #215

Open
opened 2022-11-25 12:39:57 +00:00 by yash-meesho · 1 comment
yash-meesho commented 2022-11-25 12:39:57 +00:00 (Migrated from github.com)

For example concurrenthashset.go, concurrentpriorityqueue.go?

  • Those who want performance above everything or don't have a use case can very well use the existing data structures
  • Those who want to use these data structures in production will require concurrent data structures

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

For example `concurrenthashset.go`, `concurrentpriorityqueue.go`? - Those who want performance above everything or don't have a use case can very well use the existing data structures - Those who want to use these data structures in production will require concurrent data structures 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
emirpasic commented 2023-01-04 19:46:36 +00:00 (Migrated from github.com)

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

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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
golibs/gms-gods#215
No description provided.