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

[nll] do another crater run and check the results #53171

Closed
nikomatsakis opened this issue Aug 7, 2018 · 2 comments
Closed

[nll] do another crater run and check the results #53171

nikomatsakis opened this issue Aug 7, 2018 · 2 comments
Labels
NLL-complete Working towards the "valid code works" goal T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Milestone

Comments

@nikomatsakis
Copy link
Contributor

We have almost fixed all the problems we found in the last crater run. We should do another cargo check run at some point. We need to have the -Zborrowck=mir -Ztwo-phase-borrows options supplied by default.

Once the crater run is done, we have to analyze the results.

cc @Mark-Simulacrum for advice on the best way to do that, do we need to make a PR with those options enabled by default?

@nikomatsakis nikomatsakis added I-nominated T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. NLL-complete Working towards the "valid code works" goal labels Aug 7, 2018
@nikomatsakis nikomatsakis added this to the Rust 2018 RC milestone Aug 7, 2018
@Mark-Simulacrum
Copy link
Member

That's probably the easiest way to get what we want, yes.

@nikomatsakis
Copy link
Contributor Author

I'm going to close this -- @lqd did the crater run, and we've analyzed the results and opened the requisite issues. The following links contain the analyzed results:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NLL-complete Working towards the "valid code works" goal 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

2 participants