by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qtʼs foreach rewites the code Qtʼs recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what youʼre getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qtʼs own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt’s foreach rewites the code Qt’s recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you’re getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt’s own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms

by defaulting to in-place access. For this reason range-based iterators should always be used for STL containers, if those are ever needed in Krita. Drawbacks: By default, Qt's foreach rewites the code Qt's recommendation on the other hand is to use foreach() for Qt iterators, and range-based for on STL containers, because you always know what you're getting, and you always keep your syntax easy to read m/] Historically Qt provided its own algorithm library, but now encourages programmers to use the STL versions instead, and Qt's own algorithm library will mostly become deprecated. https://doc.qt.io/qt-5/qtalgorithms