summaryrefslogtreecommitdiffstats
path: root/dependencies.yaml
diff options
context:
space:
mode:
authorMarc Mutz <marc.mutz@qt.io>2023-08-10 22:58:07 +0200
committerQt Cherry-pick Bot <cherrypick_bot@qt-project.org>2023-08-15 17:19:06 +0000
commitead57cc7431e80d7ad9b78dfd502f884cbb76a6b (patch)
tree52de6d9e56103c88203067c6e87c696ffa363814 /dependencies.yaml
parenta0b845f78c031a62d02883889bc6c3effa2d2b9e (diff)
QBluetoothUuid: cut out the streamingOperator() middle-man
The split into an inline friend op<< and an out-of-line streamingOperator() just causes the QDebug object to be copied once more than otherwise necessary. Relegate the streamingOperator() middle-man to QT_REMOVED_SINCE status and make op<< the real thing. We can't make the named function call op<<, because Thiago says there are situations in which the op<<(QDebug, QBluetoothUuid) call in removed_api.cpp, if we were to use it, would get resolved to an exported version of the old op<< in a user library compiled without -fvisibility-hidden, creating a cycle. Fortunately, the implementation is simple enough to make a DRY violation acceptable. Problem exists in 6.5, too, but let's get as many removed_api.cpp tasks done for 6.6, because the QT_NO_INT128 in removed_api.cpp will make a QT_REMOVED_SINCE(6, 7) in this header file that much harder. Change-Id: I10b42cfc1565db8d9a6924cee0af8fb6623c9000 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Alex Blasche <alexander.blasche@qt.io> (cherry picked from commit a16133c959151892a386204aa54c8115992c1075) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Diffstat (limited to 'dependencies.yaml')
0 files changed, 0 insertions, 0 deletions