3 ms·
Closures still borrow whole structs from the captured scope when they could only borrow the fields they actually need: https://play.rust-lang.org/?gist=26b2efa
by Sharlin 9y ago
Closures still borrow whole structs from the captured scope when they could only borrow the fields they actually need:
https://play.rust-lang.org/?gist=26b2efa859589a8172cad982f0dfb89b&version=stable https://play.rust-lang.org/?gist=26b2efa859589a8172cad982f0d...
This is especially frustrating when it's self that is being captured. There's an accepted RFC for fixing this but I'm not sure when it's going to be implemented.
- vvanders 9y agoYou can work-around that by capturing the fields you need individually. It's a little awkward but does let you express what you're trying to do there: https://play.rust-lang.org/?gist=2463ff559d7f96f916d246272b19ff68&version=stable https://play.rust-lang.org/?gist=2463ff559d7f96f916d246272b1... Agreed that it's not the best default behavior though. Generally I tend to try to keep unrelated things in separate structs for this reason(with the nice side benefit of keeping concerns separate).