Refactoring to have a lockfree package #76
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Based on #67)
This PR aims to reorganize the repository to make two packages and prepare for the addition of lock-based and blocking data-structures.
saturn_lockfree: contains onlylockfreedata structures ;saturn: contains the "default" data structures. Right now, it is mostly the ones insaturn_lockfreeexcept from a sub-module ofRelaxed_queue. However, in some future, we could have alock-basedimplementation that we would recommend to use by default over the lock-free one.Questions
Saturn_lockfreebut the library itself is calledlockfree. Is this ok ?lockfreepackage that has only its own dependencies. I don't see any drawbacks, but I may be missing something. Any comments about that ?