-
Notifications
You must be signed in to change notification settings - Fork 628
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
pin-utils crate & remove glob imports #1185
Conversation
//! assert_eq!(6, *block_on(shared1)); | ||
//! assert_eq!(6, *block_on(shared2)); | ||
//! # } | ||
//! ``` |
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 removed this module description because module is private and we don't have descriptions in the other modules.
@@ -12,11 +12,6 @@ | |||
|
|||
#![doc(html_root_url = "https://rust-lang-nursery.github.io/futures-doc/0.3.0-alpha.2/futures_channel")] | |||
|
|||
#[cfg(feature = "std")] |
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.
Oh, I didn't think about that. We'll have to take care not to accidentally use std
symbols in our no_std
build, because there won't be anything preventing them in CI (since std
is still reachable via a path).
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'm pretty sure that this will catch them:
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.
Yeah, that'd get it. I opened rust-lang/rust#53166 to discuss this.
Thanks, this looks great! |
pin-utils
crateextern crate
statementsuse
statements to import macrosuse futures::prelude::*
statements from code examples