Skip to content
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

Upgrade libuv to the current master (again) #8994

Closed
wants to merge 1 commit into from

Conversation

alexcrichton
Copy link
Member

This is a reopening of the libuv-upgrade part of #8645. Hopefully this won't
cause random segfaults all over the place. The windows regression in testing
should also be fixed (it shouldn't build the whole compiler twice).

A notable difference from before is that gyp is now a git submodule instead of
always git-cloned at make time. This allows bundling for releases more easily.

Closes #8850

@huonw
Copy link
Member

huonw commented Sep 5, 2013

Needs a rebase.

@alexcrichton
Copy link
Member Author

Nothing like conflicting with yourself, should be good to go now

@alexcrichton
Copy link
Member Author

This will likely have to rebase against rt-dns, but I'm more than willing to!

@anasazi
Copy link
Contributor

anasazi commented Sep 6, 2013

Out of curiosity, what's the new stuff in libuv that this brings in?

@alexcrichton
Copy link
Member Author

This is mostly an update to master libuv so we can continue to track on it, but @olsonjeffery was saying that file stat has improved a lot and libuv has also changed how they do error handling a fair amount.

There's also a bug which fixes deadlock on process spawning, but that's not in libuv master just yet and is only present in my own fork (there's a libuv issue open about it).

@anasazi
Copy link
Contributor

anasazi commented Sep 6, 2013

Do we need to rewrite all our error handling in the runtime then?

@alexcrichton
Copy link
Member Author

Oh it's not that drastic, beforehand you had to have a uv_loop_t handle to get the last error, now the error is derived from the error returned by each individual function. I updated everything in this pull as well.

This is a reopening of the libuv-upgrade part of rust-lang#8645. Hopefully this won't
cause random segfaults all over the place. The windows regression in testing
should also be fixed (it shouldn't build the whole compiler twice).

A notable difference from before is that gyp is now a git submodule instead of
always git-cloned at make time. This allows bundling for releases more easily.

Closes rust-lang#8850
bors added a commit that referenced this pull request Sep 6, 2013
This is a reopening of the libuv-upgrade part of #8645. Hopefully this won't
cause random segfaults all over the place. The windows regression in testing
should also be fixed (it shouldn't build the whole compiler twice).

A notable difference from before is that gyp is now a git submodule instead of
always git-cloned at make time. This allows bundling for releases more easily.

Closes #8850
@bors bors closed this Sep 6, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Aug 8, 2024
Add lint for `unused_result_ok`

This PR adds a lint to capture the use of `expr.ok();` when the result is not _really_ used.

This could be interpreted as the result being checked (like it is with `unwrap()` or `expect`) but
it actually only ignores the result.

`let _ = expr;` expresses that intent better.

This was also mentionned in rust-lang#8994 (although not being the main topic of that issue).

changelog: [`misleading_use_of_ok`]: Add new lint to capture `.ok();` when the result is not _really_ used.
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.

Use external gyp
4 participants