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

dropck: uses of terms "superregion" and "subregion" suboptimal #22171

Closed
pnkfelix opened this issue Feb 11, 2015 · 3 comments
Closed

dropck: uses of terms "superregion" and "subregion" suboptimal #22171

pnkfelix opened this issue Feb 11, 2015 · 3 comments
Assignees
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@pnkfelix
Copy link
Member

Spawned off of: #21022 (comment) , #21972

The dropck code (RFC 769) added a new SubregionOrigin variant for lifetime-inference errors, but the error message it reports is probably not written in terms we want to expose to our end users.

(However, this may be a moot issue since pnkfelix has most often seen the lifetime constraints added by dropck as leading to other lifetime-inference errors, and so he does not actually have a test case available at the moment that illustrates this issue.)

@steveklabnik steveklabnik added A-diagnostics Area: Messages for errors, warnings, and lints A-docs and removed A-docs labels Feb 13, 2015
@pnkfelix
Copy link
Member Author

cc #22321

@steveklabnik
Copy link
Member

Triage: over a year later, do you still feel this might be moot, @pnkfelix ? or a test case?

@steveklabnik steveklabnik added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Mar 9, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-enhancement Category: An issue proposing an enhancement or a PR with one. label Jul 22, 2017
@pnkfelix pnkfelix self-assigned this Sep 21, 2018
@pnkfelix
Copy link
Member Author

pnkfelix commented Oct 3, 2018

I continue to see no instances of this diagnostic arising.

I'm thinking I might close this issue, though I might first want to confirm that the code in question is going to be completely obsoleted by NLL anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. 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

3 participants