Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When usages of
QVector
were replaced withstd::vector
in the Core in #6477, some methods that now returnconst std::vector&
were left unchanged at the call sites. In many cases, the const reference returned by these methods was stored by value instead of by const reference. Because theQVector
objects are implicitly shared and have copy-on-write behavior, this previously didn't really matter and was a constant time operation when the objects were only read from - as was the case most of the time. But now withstd::vector
, all of thesestd::vector
objects are being deep copied which is O(n) and is not real-time safe.This PR fixes that oversight by using references at the call sites.