Skip to content

Move concurrent stuff from lib extra on a separate package #11910

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

Closed
wants to merge 3 commits into from

Conversation

jeremyletang
Copy link
Contributor

Just some work for #8784.

Move extra::arc, extra::sync, extra::future, extra::task_pool and extra::comm in libconcurrency.

maybe the name lib concurrency is not really good, but i can change this.

*/

#[allow(missing_doc)];
#[feature(globs)];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to remove this feature? If it's super painful, then we can leave it, but in general it'd be nice if the smaller crates didn't have lots of extra features.

@alexcrichton
Copy link
Member

This is pretty awesome, thanks!

I feel like the name concurrency is a little too long for a crate name. I was thinking this would be called libsync, and then it would have almost everything re-exported at the top level instead of having use sync::sync::Mutex.

What do you think of that?

@flaper87
Copy link
Contributor

FWIW, I agree w/ @alexcrichton about libsync

Change concurrency to sync,
remove extra features,
update comments (remove extern mod …).
@jeremyletang jeremyletang deleted the move-arc branch January 30, 2014 03:07
@jeremyletang jeremyletang restored the move-arc branch January 30, 2014 03:07
@jeremyletang jeremyletang deleted the move-arc branch January 30, 2014 04:30
flip1995 pushed a commit to flip1995/rust that referenced this pull request Apr 18, 2024
…ndomDev99

fix: incorrect suggestions when `.then` and `.then_some` is used

fixes rust-lang#11910

In the current implementation of `search_is_some`, if a `.is_none` call is followed by a `.then` or `.then_some` call, the generated `!` will incorrectly negate the values returned by the `then` and `.then_some` calls. To fix this, we need to add parentheses to the generated suggestions when appropriate.

changelog: [`search_is_some`]: add parenthesis to suggestions when appropriate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants