When does a deep copy happen to a QList?
Asked Answered
B

3

11

In a class I'm working on, I am juggling several QLists. I have heard that Qt tries not to make deep copies of lists whenever possible. From what I understand, that means that no deep copy happens when you do this:

QList<int> myList;
myList << 1 << 2 << 3 << 4;
QList<int> otherList = myList;  // No deep copy

In some cases, I need to make sure a deep copy never happens to the QList. Exactly what kind of operation or action do I need to make sure to avoid in order to make sure a deep copy never happens to a QList I'm working with?

Beep answered 28/7, 2011 at 21:48 Comment(0)
F
13

QLists are implemented using implicit sharing.

Object assignment (with operator=()) for implicitly shared objects is implemented using shallow copies.

This means that assignment alone will never cause the contained data to be copied. However, writing to a shared instance will cause the source object to be copied. This pattern is commonly known as copy-on-write.

So, to answer your question, if you never write to shared instances then they will never be copied. If you want to completely prevent copies being made then derive from QList and override and hide the copy constructor and assignment operator.

Forepaw answered 28/7, 2011 at 22:0 Comment(0)
T
2

When you pass a QList as a argument of a function or when you create copies without modifying it Qt just pass a "wrapper", the real data is never copied along. Implicit sharing is the Qt implementation of the Flyweight pattern, see here.

Termless answered 29/7, 2011 at 1:15 Comment(0)
C
1

Just make sure to use constBegin(), constEnd(), pass by const reference, don't modify or copy.

Crownpiece answered 14/7, 2015 at 15:45 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.