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

Cross-crate unboxed closures are not fully implemented #18543

Closed
bkoropoff opened this issue Nov 2, 2014 · 0 comments · Fixed by #18546
Closed

Cross-crate unboxed closures are not fully implemented #18543

bkoropoff opened this issue Nov 2, 2014 · 0 comments · Fixed by #18546

Comments

@bkoropoff
Copy link
Contributor

tcx.sess.bug("unimplemented cross-crate closure upvars")

Users will start running into this once #18378 is fixed

bkoropoff added a commit to bkoropoff/rust that referenced this issue Nov 2, 2014
Always translate the ID into the local crate ID space since
presently the only way to encounter an unboxed closure type
from another crate is to inline once of its functions.

This may need to change if abstract return types are added.

Closes rust-lang#18543
bors added a commit that referenced this issue Nov 5, 2014
…=nick29581

This fixes some metadata/AST encoding problems that lead to ICEs.  The way this is currently handled will need revisiting if abstract return types are added, as unboxed closure types from extern crates could show up without being inlined into the local crate.

Closes #16790 (I think this was fixed earlier by accident and just needed a test case)
Closes #18378
Closes #18543

r? @pcwalton
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 a pull request may close this issue.

1 participant