As decided with lazy consensus on the development ML¹, we'd like to separate precondition checking from internal consistency checking. Add a new Q_PRE/Q_PRE_X macro for the former, to leave Q_ASSERT/_X for the latter. As requested in review, modernize Q_PRE_X vis-a-vis Q_ASSERT_X by skipping the `where` parameter (defaulting it to Q_FUNC_INFO). Added as undocumented API, for now, to pick back to all active branches without actually promising semantics different from Q_ASSERT, a change that, realistically, will only happen for 6.10 at the earliest. But by making the macro available to all active branches, we avoid conflicts when picking changes back, and the change is rather risk-less. Apply to QStringView, to have at least one user. ¹ https://lists.qt-project.org/pipermail/development/2024-August/045588.html Items 1-3. Pick-to: 6.8 6.5 Task-number: QTBUG-98965 Change-Id: Ia04248a64c8feba80cce10f8f5cbde580436db88 Reviewed-by: Jøger Hansegård <joger.hansegard@qt.io> Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> (cherry picked from commit eb3df4edbc0ca04a892728e54962ad0daef4a78e) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
…
…
Description
Languages
C++
84.3%
HTML
4.9%
C
3.9%
CMake
3.6%
Objective-C++
2%
Other
0.8%