We could create a MoveGuard, similar to ReentrancyGuard, that sets a `moved = true` flag in debug builds and make methods assert against that.
(But it isn't nearly as nice as having borrowck...) On Wed, Apr 27, 2016 at 5:53 PM, smaug <sm...@welho.com> wrote: > On 04/28/2016 08:00 AM, Gerald Squelart wrote: > > Because sometimes the function will choose not to actually move from an >> rvalue-ref >> > > FWIW, this is the reason why I think Move is broken by definition. Move > doesn't move anything. > It should have been designed differently, so that a temporary object is > created to ensure move is always happening or something like that > (though, that might lead to leaks in some cases). > > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
