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

usleep is broken and should not be used #12689

Closed
thestinger opened this issue Mar 4, 2014 · 0 comments
Closed

usleep is broken and should not be used #12689

thestinger opened this issue Mar 4, 2014 · 0 comments

Comments

@thestinger
Copy link
Contributor

It was actually removed from POSIX since it can't be used correctly. There's no way of sleeping until the time is elapsed as it doesn't report the elapsed time on EINTR. Instead, clock_nanosleep or nanosleep should be used.

bors added a commit to rust-lang-ci/rust that referenced this issue Jul 25, 2022
internal: Record all macro definitions in ItemScope

Fixes rust-lang/rust-analyzer#12100

Doesn't resolve the shadowing issues though, fixing those is gonna be really tricky I believe unless we can come up with a nice scheme to "order" item tree items (using syntax ranges and file ids would be a pain and also a bad idea since that'll require us to potentially reparse files in collection).
flip1995 pushed a commit to flip1995/rust that referenced this issue Jun 13, 2024
…archo

[`overly_complex_bool_expr`]: Fix trigger wrongly on never type

fixes rust-lang#12689

---

changelog: fix [`overly_complex_bool_expr`] triggers wrongly on never type
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

No branches or pull requests

1 participant