Similar to #69, but implementation is better. Moving forward the solution should always follow range rules, BUT make sure to renew the internal iterator in postblit to make sure the copied struct has a new iterator. Probably should also add reference counting.
Similar to #69, but implementation is better. Moving forward the solution should always follow range rules, BUT make sure to renew the internal iterator in postblit to make sure the copied struct has a new iterator. Probably should also add reference counting.