-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support Arc in addition to Rc and & #19
Comments
Is there a reason (besides avoiding code duplication) that this feature is blocked on GATs landing? |
It's a combination of code duplication and lack of development time. I have a branch with a near-complete refactor somewhere that would minimize the duplication, but it changes the API somewhat so I've been waiting for the opportunity to collect some feedback before pulling the trigger. The change (described in this thread) would allow for the removal of virtual dispatch, make it easier to make a In the meantime, if someone were to submit a PR adding support for |
You might want to take a look at archery. (Disclaimer: I'm the author 🙂) |
I think being able to share the Pool itself across threads will also be nice too. Currently Pool is not Sync as it uses an Rc/RefCell internally. |
After some experimentation on a local branch, benchmarks show that using an This single-threaded benchmark simply allocated blank
Note that the I'd still like to offer this feature, but I'll need to look into other concurrency strategies. |
Pool
values are currently neitherSend
norSync
, which precludes some interesting use cases aroundrayon
andcrossbeam
.Add support for creating a
Pool
that emitsArc
references once Generic Associated Types (rust-lang/rust/issues/44265) lands.The text was updated successfully, but these errors were encountered: