-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rust 1.18 regression - mime_multipart-0.3.5 #40958
Labels
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
alexcrichton
added
the
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
label
Mar 31, 2017
brson
added
the
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
label
Apr 4, 2017
|
alexcrichton
added
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
and removed
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
labels
Apr 4, 2017
Signature of pub fn parse_headers<'b: 'h, 'h>(src: &'b [u8], mut dst: &'h mut [Header<'b>]) This was caused by #40319 and indeed discussed in the thread with the author: #40319 (comment). |
OK, closing this issue then. |
@mikedilger you may wish to publish the new versions of the crate, if you've not already done so. |
@nikomatsakis New versions were published 9th of March. I hope 0.3.5 doesn't get pulled into regression testing of each subsequent rust version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Regression logs
This looks like a soundness fix, but this'll track ensuring we send a PR upstream and file this into the release notes.
The text was updated successfully, but these errors were encountered: