diff options
| author | bors <bors@rust-lang.org> | 2015-01-01 04:01:02 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-01-01 04:01:02 +0000 |
| commit | 47b8479e73e40395f1b1b2d0c6281f28f80301e4 (patch) | |
| tree | a8ae69e94286da9d3b153e39300130271ad1f3f8 /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 7d4f4876d65bddf101784230c0347adcb01e5c21 (diff) | |
| parent | 10bbf69488b4863378e4acd9d55bde36b4a20909 (diff) | |
| download | rust-47b8479e73e40395f1b1b2d0c6281f28f80301e4.tar.gz rust-47b8479e73e40395f1b1b2d0c6281f28f80301e4.zip | |
auto merge of #20363 : japaric/rust/moar-uc, r=nmatsakis
The the last argument of the `ItemDecorator::expand` method has changed to `Box<FnMut>`. Syntax extensions will break.
[breaking-change]
---
This PR removes pretty much all the remaining uses of boxed closures from the libraries. There are still boxed closures under the `test` directory, but I think those should be removed or replaced with unboxed closures at the same time we remove boxed closures from the language.
In a few places I had to do some contortions (see the first commit for an example) to work around issue #19596. I have marked those workarounds with FIXMEs. In the future when `&mut F where F: FnMut` implements the `FnMut` trait, we should be able to remove those workarounds. I've take care to avoid placing the workaround functions in the public API.
Since `let f = || {}` always gets type checked as a boxed closure, I have explictly annotated those closures (with e.g. `|&:| {}`) to force the compiler to type check them as unboxed closures.
Instead of removing the type aliases (like `GetCrateDataCb`), I could have replaced them with newtypes. But this seemed like overcomplicating things for little to no gain.
I think we should be able to remove the boxed closures from the languge after this PR lands. (I'm being optimistic here)
r? @alexcrichton or @aturon
cc @nikomatsakis
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
