Skip to content

Fix some cross-crate unboxed closure bugs #18546

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 3 commits into from
Nov 5, 2014

Conversation

bkoropoff
Copy link
Contributor

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

Closes rust-lang#18378.  Note that cross-crate unboxed closures are
still unimplemented and will fail to work currently.
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
@brson
Copy link
Contributor

brson commented Nov 4, 2014

Sweet 🍬

bors added a commit that referenced this pull request 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
@bors bors closed this Nov 5, 2014
@bors bors merged commit bfa5320 into rust-lang:master Nov 5, 2014
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
6 participants