On Sunday 11 August 2024 10:31:06 GMT-7 Thiago Macieira wrote: > It might be possible to consult the string array and avoid having to have > string indices all over the place. This will require some more testing, > especially with the QtOpcUA::NodeIds massive listing. > > I may have a line of sight to generating the string table, but that > definitely requires C++20 for the ability to have literal types in template > parameters.
Update: I had to rewrite the code that was using std::tuple with our own, hand-rolled template pack holder because libstdc++'s std::tuple causes GCC to run out of memory and go into swap hell, while Clang sops at a hard limit (libc++'s std::tuple isn't affected). But I managed to make it work and compile with VS2022, Clang 18, GCC 14, and whatever Clang comes with XCode. I even got the metatype support I mentioned above working. I'm running it through the CI now to see if there's anything I missed and if QNX and INTEGRITY will join us or if they will keep the old moc- generated content. I will not spend any time at all trying to understand problems exclusive to them. The compilation times are expected to increase, but not by much. I tested tst_qstringapisymmetry, which has 787 slots, and compilation times went up between 6.5 and 10% (tested in debug mode). -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
