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.

Sign up for GitHub

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

Jump to bottom

Remove the many subMapMutex.Lock(), Unlock() calls, possibly #8

Closed
cameronelliott opened this issue Apr 17, 2021 · 1 comment
Closed

Remove the many subMapMutex.Lock(), Unlock() calls, possibly #8

cameronelliott opened this issue Apr 17, 2021 · 1 comment

Comments

@cameronelliott
Copy link
Member

Because of the nature of Go maps, iterating the subscribe set means a fair number
of subMapMutex.Lock(), Unlock() calls

It might be cleaner to translate the subscriber uniq id to an array/slice index, which
then gets iterated, skipping empties.
@cameronelliott cameronelliott changed the title Remove the many subMapMutex.Lock(), Unlock() calls Remove the many subMapMutex.Lock(), Unlock() calls, possibly Apr 17, 2021
@cameronelliott
Copy link
Member Author

no longer relevat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cameronelliott