As a user has pointed out in this issue, the take_mut crate contains a potential memory leak and appears to be abandoned. While our usage of the crate does not touch the method with the potential memory leak, we should still consider removing the dependency because of its expansive usage of unsafe code along with its unmaintained status. This would require some internal refactoring to allow a &mut T to be taken; we could potentially switch to using {{Option}}s or create an internal API to emulate such functionality.