Qt Contributor Summit 2019 - QtCore

Session notes.

Recap:

• https://bugreports.qt.io/browse/QTBUG-71036

Containers

QList = QVector by default in Qt 6

s/QList/QVector/g before Qt 6 releaase to avoid merging nightmare

Not sure if to keep Qt5List. We need more evaluation about how much code breaks (e.g. when Creator, KDE port it)

QPair=std::pair => no brainer

QHash in terms of std::unordered_map: Lars, Peppe experimented on it, it "works", esp. after

Concerns regards std::unordered_map itself -- it's not great. Should we look at other unorderd_map implementations?

QMap => std::map, yes

QLinkedList => Qt5LinkedList

(Need to clarify what ends up in a Qt5Support library)

Do we need to provide generic accessors for arbitrary containers, esp. in the light of ranges added to C++20? (And what about things like toSet, toList, etc.?) Concerns raised by starting including std headers all over the place.

Codecs

Legacy text codecs implementations in Qt are going to be dropped from Qt itself; anything but UTF- codecs will require 3rd party (ICU).

Threading

• QRecursiveMutex split from QMutex
• QWaitCondition & QReadWriteCondition improvements?
• Future of QFuture

Other

• Regexp
  • P0169R0 - regex with Unicode character types
  • P1844R0 - Enhancement of regex