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

borrowck changes #65527

Closed
Mark-Simulacrum opened this issue Oct 17, 2019 · 7 comments
Closed

borrowck changes #65527

Mark-Simulacrum opened this issue Oct 17, 2019 · 7 comments
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

@Mark-Simulacrum Mark-Simulacrum added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. regression-from-stable-to-beta Performance or correctness regression from stable to beta. labels Oct 17, 2019
@Mark-Simulacrum Mark-Simulacrum added this to the 1.39 milestone Oct 17, 2019
@ecstatic-morse
Copy link
Contributor

ecstatic-morse commented Oct 18, 2019

The errors in eggmund.Prey are a result of NLL errors becoming fatal. They existed as warnings on 1.38. This is expected breakage.

@ecstatic-morse
Copy link
Contributor

ecstatic-morse commented Oct 18, 2019

Regressions 2 and 4 are the same, occurring in soketto-0.2. I partially minimized the problem. The trait object is necessary. This is a true regression, although I think this code should never have been accepted on stable?

use std::any::Any;

fn drain_dyn(v: &mut Vec<Box<dyn Any>>) -> impl Iterator<Item = Box<dyn Any>> {    
    v.drain()
}

See #65582.

@ecstatic-morse
Copy link
Contributor

ecstatic-morse commented Oct 18, 2019

Regression 3, in gfx-rs, is also a result of NLL errors becoming fatal. This is expected breakage.

@ecstatic-morse
Copy link
Contributor

ecstatic-morse commented Oct 19, 2019

@Mark-Simulacrum I've triaged all four regressions and opened an issue for the only unexpected one. I'll close this issue in favor the new one.

@Centril Centril removed this from the 1.39 milestone Nov 7, 2019
@imclint21
Copy link

Hi @Mark-Simulacrum,

We own the repo efb9-860a-e752-0dac do you know why this log file contains our repository rustchal?

=>https://crater-reports.s3.amazonaws.com/beta-1.39-rustdoc-1/beta-2019-09-28/gh/efb9-860a-e752-0dac.rustchal/log.txt

@Mark-Simulacrum
Copy link
Member Author

Crater queries GitHub for all Rust repositories (I'm not sure on specifics of how GitHub determines that). We then build all of those repositories on our infrastructure.

@imclint21
Copy link

Oh very interesting, thank you 👌

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.
Projects
None yet
Development

No branches or pull requests

4 participants