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

Cookbook ideas for num_cpus #300

Closed
bobbo opened this Issue Sep 29, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@bobbo
Contributor

bobbo commented Sep 29, 2017

Come up with ideas for nice introductory examples of using the num_cpus crate, possibly in combination with other crates, that would be good to show in the Rust Cookbook. Please leave a comment here with your ideas! You don't necessarily have to write the example code yourself but PRs are always welcome!

EDIT:

@budziq

This comment has been minimized.

Show comment
Hide comment
@budziq

budziq Sep 29, 2017

Collaborator

@bobbo I've added a single example idea for now.
Another is to "Get number of physical cpu cores" unfortunately I do not like that the get_physical falls back to logical cores if physical cant be queried making such example unreliable (I'would suggest for this function to return a Result) I'll propose it on blitz evaluation thread.

Collaborator

budziq commented Sep 29, 2017

@bobbo I've added a single example idea for now.
Another is to "Get number of physical cpu cores" unfortunately I do not like that the get_physical falls back to logical cores if physical cant be queried making such example unreliable (I'would suggest for this function to return a Result) I'll propose it on blitz evaluation thread.

@budziq budziq added this to the impl period milestone Oct 4, 2017

@AndyGauge AndyGauge referenced this issue Apr 20, 2018

Closed

Tracking Issues #396

13 of 13 tasks complete
@AndyGauge

This comment has been minimized.

Show comment
Hide comment
@AndyGauge

AndyGauge Apr 23, 2018

Collaborator

This tracking issue seems resolved.

Collaborator

AndyGauge commented Apr 23, 2018

This tracking issue seems resolved.

@AndyGauge AndyGauge closed this Apr 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment