-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
std: Fix peeling ports from addresses #23097
Conversation
The `rsplitn` call was called with 2 instead of 1 so the iterator would yield 3 items in some cases, not the 2 that it should have. Closes rust-lang#23076
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ 65b4eda |
The `rsplitn` call was called with 2 instead of 1 so the iterator would yield 3 items in some cases, not the 2 that it should have. Closes rust-lang#23076
This seems to be causing panics within panics on Windows (only) @retep998 got a sortof-backtrace |
Note that error was from building the rollup PR which happened to include this PR. I am still working on building just this PR. Unfortunately LLVM really likes to rebuild all the time. |
Yeah, same test, just that the doublepanic doesn't happen |
This is not the cause of the double panic. |
The `rsplitn` call was called with 2 instead of 1 so the iterator would yield 3 items in some cases, not the 2 that it should have. Closes rust-lang#23076
The
rsplitn
call was called with 2 instead of 1 so the iterator would yield 3items in some cases, not the 2 that it should have.
Closes #23076