fix: copy valid range when cloning stack

When cloning a stack we are only interested in copying valid data from the original stack, not the unused/garbaged tail of it.

0 files changed, 0 insertions, 0 deletions