qt6-bb10

History

Marc Mutz e11edced7e QStringView: fix construction from arrays of unknown size The original idea (`8b5aa7b6c4`) of the separation of array and pointer ctors was to determine string literal sizes at compile-time in C++11's limited constexpr semantics. But when the scanning for NUL characters was added to the array ctor in `107ff4c1d6`, the distinction between the two ctors became meaningless, because we were able to assume post-C++11 constexpr to make the Char(0) scan a compile-time action. Finally, `9e1dc1e8a9` removed the array ctor in favor of the generic Container ctor. I didn't check whether the old code handled arrays of unknown size, as in extern const char16_t str[]; QStringView sv = str; ~~~ const char16_t str[] = "str"; but std::size() (and therefore if_compatible_container) surely bails on such arrays, and if_compatible_pointer also SFINAEs out. As a consequence, such arrays cannot be used to construct QStringViews atm. Fix by adding a new constructor for arrays of unknown size, delegating to the existing pointer overload. The GHS compiler doesn't like the CanConvert static_asserts, so comment them out for it. The functionality itself is tested by the fromArrayWithUnknownSize tests. [ChangeLog][QtCore][QStringView] Made construction from arrays of unknown size compile. Such arrays will use the const Char constructor, determining the size of the array at runtime. Pick-to: 6.5 Task-number: QTBUG-112746 Change-Id: Ifdb217350d93d38f081c99f14661975491d32076 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 56faffd92bf0ac459a921ec043a6f3b3dba51acc) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 2dfc0cb6f6f1e29a0a1318793b29b89390543be6)		2024-12-13 08:00:15 +00:00
..
auto	QStringView: fix construction from arrays of unknown size	2024-12-13 08:00:15 +00:00
baseline	test: baseline: Call finalizeAndDisconnect	2024-11-22 20:18:50 +00:00
benchmarks	Add REUSE.toml files	2024-11-07 08:38:49 +01:00
global	…
libfuzzer	Complete color space toICC write	2024-05-31 16:24:50 +02:00
manual	iconbrowser test: URI-encode the remote path	2024-11-13 18:04:25 +00:00
shared	Replace incorrect Metal config check in nativewindow.h	2024-05-01 14:24:06 +02:00
testserver	Add REUSE.toml files	2024-11-07 08:38:49 +01:00
CMakeLists.txt	Rid of 'special case' markers	2023-04-13 18:30:58 +02:00
README	…

README

This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.

Linux X11:

   * The user must be logged in to an active desktop; you can't run the
     autotests without a valid DISPLAY that allows X11 connections.

   * The tests are run against a KDE3 or KDE4 desktop.

   * Window manager uses "click to focus", and not "focus follows mouse". Many
     tests move the mouse cursor around and expect this to not affect focus
     and activation.

   * Disable "click to activate", i.e., when a window is opened, the window
     manager should automatically activate it (give it input focus) and not
     wait for the user to click the window.