Re:Lambda expression comparison between C++11, C++14 and C++17
by hendzen on Saturday May 14, 2016 @06:20PM
(#11698317)
How would you do the equivalent of this in Rust?
[ Parent
| on HN ]
Re:Lambda expression comparison between C++11, C++14 and C++17
by steveklabnik on Saturday May 14, 2016 @06:22PM
(#11698323)
let on_heap = Box::new(...);
function_that_accepts_lambda(move || {
on_heap.bar();
});
This is sort of what kibwen was mentioning: move is a single annotation that overrides everything to capture by value rather than have it inferred.
Re:Lambda expression comparison between C++11, C++14 and C++17
by hendzen on Saturday May 14, 2016 @06:39PM
(#11698383)
What if you want to move some things, but copy others?
e.g.
auto shared = std::make_shared<MySharedType>(...);
auto unique = std::make_unique<MyOwnedType>(...);
function_that_accepts_lambda([shared, u = std::move(unique)] {
shared->foo(...); u->bar(...);
});
// Outer scope can still use shared.
shared->foo(....);
Re:Lambda expression comparison between C++11, C++14 and C++17
by steveklabnik on Saturday May 14, 2016 @07:03PM
(#11698461)
I am 99% sure this is identical:
let on_heap = Box::new(...);
let shared = Arc::new(...);
let s = shared.clone();
function_that_accepts_lambda(move || {
on_heap.bar();
s.foo();
});
We have to make the extra s binding.Also, my sibling is correct that Copy types will just be copied, not moved.