Re:Idiomatic Monads in Rust
by 0815test on Thursday April 04, 2019 @08:16PM
(#19578441)
You could have a trait similar to Copy that forces Drop to be a no-op, and require live values that don't conform to it to be moved into any `become`.
[ Parent
| on HN ]
Or just skip the trait and require there to be nothing live on the stack that conforms to Drop after a `become`.
In fact, the main reason to have a keyword like `become` is to signal to the compiler to do this kind of analysis, because it's so easy to accidentally break the ability to do TCO when you can't lean on a GC to clean things up later.