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.
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
Add
Ref
to thesync
module. #141Add
Ref
to thesync
module. #141Changes from all commits
c73b81e
9b8feeb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since everything just accesses
.count
, would it make more sense to have this->&AtomicUsize
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think an opaque
RefCount
is better for a couple of reasons:RefCount
didn't have any constructors: the only way to get one [outside the module] was throughRef::try_new
, which took a closure as argument that had aRefCount
as argument and returnedT
(which would then be wrapped inRef
). This was my attempt at enforcing that all instances ofT
be wrapped inRef
. It didn't really guarantee it because one could just 'exfiltrate' theRefCount
instance and use it to build an unsafeT
(it could never return because it wouldn't be able to construct theT
that it needs to return, but one could exfiltrateT
to another thread and sleep forever). This is a convoluted way to build an unsafe program, but it is a way nonetheless, so I had to makeRefCounted
an unsafe trait. Anyway, I still hope we'll find a way to implement this safely and makeRefCounted
safe; not allowingRefCount
to be arbitrarily constructed may be part of the solution.