The automatically generated drop shims perform a
Rawretag of their argument because they use it as a raw pointer.
Does this also applies for
Drop::drop(&mut self) ? Or why does this behave differently ?
Drop::drop is not the automatically generated drop shim
that would be
Is the automatically generated drop shim called at the end / after
Drop types? I don't know how this works.
the drop shim calls
and then proceeds to recursively call the drop shim for the fields