aa37e67ef7
We've been requiring C++17 since Qt 6.0, and our qAsConst use finally starts to bother us (QTBUG-99313), so time to port away from it now. Since qAsConst has exactly the same semantics as std::as_const (down to rvalue treatment, constexpr'ness and noexcept'ness), there's really nothing more to it than a global search-and-replace, with manual unstaging of the actual definition and documentation in dist/, src/corelib/doc/ and src/corelib/global/. Task-number: QTBUG-99313 Change-Id: I4c7114444a325ad4e62d0fcbfd347d2bbfb21541 Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| gradientgen.cpp | ||
| gradientgen.js | ||
| gradientgen.pro | ||
| package-lock.json | ||
| package.json | ||
| qt_attribution.json | ||
| README | ||
| WEBGRADIENTS_LICENSE.txt | ||
| webgradients.css | ||
Regeneration of gradients: 0) Grab a new .css for the webgradients 1) Run the gradientgen.js script (requires node): gradientgen.js enum webgradients.css # will regen the enumeration names (on stdout) gradientgen.js json webgradients.css # will regen the actual gradients (on stdout) 2) Build gradientgen.pro 3) Run gradientgen, passing the json as stdin, the result will be on stdout