On Monday, 14 November 2022 23:52:23 PST Marc Mutz via Development wrote: > Unless and until we replace all QString/QStringView overload sets with a > single QAnyStringView function (possibly accompanied by a QString > Q_WEAK_OVERLOAD), we can't make QString implicitly convertible from > char16_t literals. While we can QT_REMOVED_SINCE our own API, we can't > do the same for user API that relies on the explicit guarantee of > QString/QStringView overloadability.
And then there's user library code. Our changing this would affect them, unless they make the same type of change that we do. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
