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

Rollup of 11 pull requests #35893

Closed
wants to merge 25 commits into from
Closed

Rollup of 11 pull requests #35893

wants to merge 25 commits into from

Conversation

munyari and others added 25 commits August 11, 2016 10:01
Issue rust-lang#35799 as a part of issue rust-lang#35233
?r jonathandturner
Based on following what happens in CString::new("string literal"):

1. Using `Into<Vec<u8>>`, a Vec is allocated with capacity exactly equal
   to the string's input length.
2. By `v.push(0)`, the Vec is grown to twice capacity, since it was full.
3. By `v.into_boxed_slice()`, the Vec capacity is shrunk to fit the length again.

If we use `.reserve_exact(1)` just before the push, then we avoid the
capacity doubling that we're going to have to shrink anyway.

Growing by just 1 byte means that the step (2) is less likely to have to
move the memory to a larger allocation chunk, and that the step (3) does
not have to reallocate.
It used to say "Furtheremore" instead of "Furthermore".
This fixes rust-lang#35849, a regression introduced by the typeck refactoring
around TyNever/!.
…urner

New format for E0426

Issue rust-lang#35799 as a part of issue rust-lang#35233
r? jonathandturner
…umeGomez

Indicate where `core::result::IntoIter` is created.

None
…r=alexcrichton

Check that executable file is in-tree before failing tidy check

I silenced stdout and stderr for ls-files, not sure if that's appropriate (is `make tidy` intended to give debugging information)? Otherwise it prints each file it find to stdout/stderr, which currently prints nothing (only executable files are checked).

I have not done major testing regarding the behavior of ls-files when the file is ignored, but judging by the man page everything should be fine.

I've duplicated the code which makes the path git-friendly from the `Cargo.lock` checking code; I can extract that into a common helper if wanted (it's only two lines).

Fixes rust-lang#35689.
cstring: avoid excessive growth just to 0-terminate

Based on following what happens in CString::new("string literal"):

1. Using `Into<Vec<u8>>`, a Vec is allocated with capacity exactly equal
   to the string's input length.
2. By `v.push(0)`, the Vec is grown to twice capacity, since it was full.
3. By `v.into_boxed_slice()`, the Vec capacity is shrunk to fit the length again.

If we use `.reserve_exact(1)` just before the push, then we avoid the
capacity doubling that we're going to have to shrink anyway.

Growing by just 1 byte means that the step (2) is less likely to have to
move the memory to a larger allocation chunk, and that the step (3) does
not have to reallocate.

Addresses part of rust-lang#35838
Fix "Furthermore" Typo in String Docs

It used to say "Furtheremore" instead of "Furthermore".
typeck: use NoExpectation to check return type of diverging fn

Fixes rust-lang#35849.

Thanks @eddyb.
@rust-highfive
Copy link
Collaborator

r? @brson

(rust_highfive has picked a reviewer for you, use r? to override)

@eddyb
Copy link
Member Author

eddyb commented Aug 22, 2016

@bors r+ p=1

@bors
Copy link
Contributor

bors commented Aug 22, 2016

📌 Commit dd5137b has been approved by eddyb

@bors
Copy link
Contributor

bors commented Aug 22, 2016

⌛ Testing commit dd5137b with merge aaad88b...

@bors
Copy link
Contributor

bors commented Aug 22, 2016

💔 Test failed - auto-mac-64-opt

@eddyb
Copy link
Member Author

eddyb commented Aug 22, 2016

Ughhh - and I did check that travis passed on each PR.

@eddyb eddyb closed this Aug 22, 2016
@Centril Centril added the rollup A PR which is a rollup label Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup
Projects
None yet
Development

Successfully merging this pull request may close these issues.