Skip to content

Don't call new closures "unboxed" wherever possible. #21598

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

Merged
merged 5 commits into from
Jan 26, 2015

Conversation

eddyb
Copy link
Member

@eddyb eddyb commented Jan 24, 2015

No description provided.

@rust-highfive
Copy link
Contributor

r? @nick29581

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

@brson
Copy link
Contributor

brson commented Jan 25, 2015

Great cleanup, thanks.

@eddyb
Copy link
Member Author

eddyb commented Jan 25, 2015

@bors r=brson ed9d014

@bors
Copy link
Collaborator

bors commented Jan 26, 2015

⌛ Testing commit ed9d014 with merge ea85c9a...

@bors
Copy link
Collaborator

bors commented Jan 26, 2015

💔 Test failed - auto-mac-64-nopt-t

@eddyb eddyb force-pushed the there-are-no-boxed-closures branch from ed9d014 to 9690be5 Compare January 26, 2015 02:15
@eddyb
Copy link
Member Author

eddyb commented Jan 26, 2015

@bors r=brson 9690be5

@bors
Copy link
Collaborator

bors commented Jan 26, 2015

⌛ Testing commit 9690be5 with merge 9252525...

@bors
Copy link
Collaborator

bors commented Jan 26, 2015

@bors bors merged commit 9690be5 into rust-lang:master Jan 26, 2015
@eddyb eddyb deleted the there-are-no-boxed-closures branch January 26, 2015 11:56
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.

5 participants