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

Cherry-picking PR 24553 into [beta] #24941

Closed
wants to merge 2 commits into from

Conversation

pnkfelix
Copy link
Member

This PR is a cherry-pick of PR #24553, which has gone through the beta-nomination and beta-acceptance process. (It just missed being part of the mass cherry-pick in #24708 because I had not yet reviewed it at that time.)

It should not be marked with the usual bors commands (i.e. no "r+" messages to at-bors); it instead will be merged manually after I had double checked that it builds locally.

table, introduce a `FreeRegionMap` data structure. regionck computes the
`FreeRegionMap` for each fn and stores the result into the tcx so that
borrowck can use it (this could perhaps be refactored to have borrowck
recompute the map, but it's a bid tedious to recompute due to the
interaction of closures and free fns). The main reason to do this is
because of rust-lang#22779 -- using a global table was incorrect because when
validating impl method signatures, we want to use the free region
relationships from the *trait*, not the impl.

Fixes rust-lang#22779.

----

This is cherry-pick of commit 6dfeda7 from PR rust-lang#24553

Manually resolved conflicts in:
  src/librustc/lib.rs
  src/librustc/middle/infer/region_inference/mod.rs
(both conflicts were related to changes to file structure.)
This is a cherry-pick of commit 55ffd2e from PR rust-lang#24553
@rust-highfive
Copy link
Collaborator

r? @nikomatsakis

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

@pnkfelix
Copy link
Member Author

@bors: try

(I am just curious whether bors can be used in this manner to give these cherry-picks to beta a whirl.)

Update: from the "Merge conflict", I infer that I should instead push to the try branch, rather than using the try request-command to bors. ... or wait, even github says there is a merge conflict right now? That's weird, I thought I was working off the latest beta branch ...)

@bors
Copy link
Contributor

bors commented Apr 29, 2015

🔒 Merge conflict

@pnkfelix pnkfelix closed this Apr 29, 2015
@pnkfelix pnkfelix reopened this Apr 29, 2015
@pnkfelix pnkfelix closed this Apr 29, 2015
@pnkfelix pnkfelix reopened this Apr 29, 2015
@pnkfelix pnkfelix closed this Apr 29, 2015
This was referenced Apr 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants