-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
deprecate std/threadpool; use malebolgia, weave, nim-taskpool instead
#22576
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
Conversation
std/threadpool; use malebolgia insteadstd/threadpool; use malebolgia, weave, nim-taskpool instead
|
I think if we are going to ship 2 package managers with Atlas, |
|
"Nimble package" means "package using the Nimble package format", which basically every Nim library is. Both package managers as well as other user package managers recognize the Nimble package format. "Use Nimble" is not necessarily implied. |
|
Is it wise to recommend people use |
No change, I didn't test Weave with arc/orc. And it doesn't call destructors for sure. I didn't test nim-taskpools either, but at least std/tasks that it relies on does call destructors. |
|
The benefits of moving libs out of std... 😇 |
|
|
Malebolgia is likely to use its own version of it, eventually... |
|
Thanks for your hard work on this PR! Hint: mm: orc; opt: speed; options: -d:release |
ref nim-lang/RFCs#503