Re: [Development] API style guide: scoped enum or not?
On 2023-05-04, Marc Mutz via Development wrote: > So, enum-backed APIs taking int will have to be ported to take the enum > instead. On the plus side, you get type-richer and safer APIs. How would you do the extensions (e.g. user roles or user events) if you convert to enums ? /Sune -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Monthly CI maintenance break - May (Mon, May 8th 2023)
This is now DONE From: Ville-Pekka Karhu Sent: Monday, May 8, 2023 08:02 To: Qt development mailing list Subject: Re: Monthly CI maintenance break - May (Mon, May 8th 2023) This starts NOW From: Ville-Pekka Karhu Sent: Tuesday, May 2, 2023 13:01 To: Qt development mailing list Subject: Monthly CI maintenance break - May (Mon, May 8th 2023) Hi, We’ll have our scheduled maintenance break on next Monday (8th of May). We’ll begin our work at 5:00 UTC and you can prepare for 6 hours of CI not working. -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] API style guide: scoped enum or not?
On Monday, 8 May 2023 00:21:32 PDT Sune Vuorela wrote: > How would you do the extensions (e.g. user roles or user events) > if you convert to enums ? Still with the enum, but you need to somewhere write extra code to cast that new number to the proper type. That's all. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Raising the minimum to C++20
For the sake of correctness... On Sat, 6 May 2023 at 12:12, Lisandro Damián Nicanor Pérez Meyer wrote: [snip] > - meta-qt6 is still buggy. Note I am not talking about boot2qt but > just using the Qt 6 layer in a normal Yocto way. Example: > QTBUG-113372: QT_HOST_PATH not set in SDK. This last part is my bad. Although maybe a room for improvement, but considering the current state of afairs, my bad. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/ -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] HEADS-UP: Qt 6.6 Feature Freeze is getting closer
Hi, Only less than 2 weeks to 'Platform and Module' freeze and ~ a month to official feature freeze. So it is time - to inform me about new modules coming in Qt 6.6 * Qt Graphs is only known one atm - to inform me if some 'TP' module will be officially supported in Qt 6.6 - to start updating new features etc in 'What' new in Qt 6.6' wiki * https://code.qt.io/cgit/qt/qtdoc.git/tree/doc/src/whatsnew/whatsnew66.qdoc br, Jani > -Original Message- > From: Jani Heikkinen > Sent: tiistai 18. huhtikuuta 2023 9.07 > To: development@qt-project.org > Subject: HEADS-UP: Qt 6.6 Feature Freeze is getting closer > > Hi all, > > > > Just a kindly reminder: Qt 6.6 Feature freeze will be in effect 2nd of June > 2023 and Qt 6.6 platform and module freeze 19th of May 2023, see > https://wiki.qt.io/Qt_6.6_Release > > > > Please inform me about all new modules planned to be released in Qt 6.6; > we should start adding those in CI & packages asap. > > Also please inform me if existing technology preview module will be officially > supported etc. > > > > br, > > Jani > > -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Proposing changes to https://wiki.qt.io/Qt_Coding_Style
Hi,
I'd like to propose the following clarifications:
- no space between "operator" and it's symbol:
// WRONG
bool operator ==()
// CORRECT
bool operator==()
Rationale: that's the style we find in all of Qt, but QtC's
auto-completion (by default?) adds the space, so we should clarify what
we want (and fix QtC).
- exactly one space each between if and constexpr/constinit and
following [({]:
// WRONG
if constinit(
if constexpr(~~~) {
// CORRECT
if constinit {
if constexpr (~~~) {
- space after template and before <:
// WRONG
template
// CORRECT:
template
Rationale: We always used the latter in Qt. Then a faulty _clang-format
that dropped the space for unknown reasons was added to qt5.git and
since then, we have a wild mix. We should fix the faulty _clang-format
file and codify just one variant in the normative document,
https://wiki.qt.io/Qt_Coding_Style.
- drop the requirement for () in lambdas
Rationale: this was a word-around for older MSVCs. The standard doesn't
require the empty parameter list (except when adorning the lambda with
noexcept etc, and then the compiler complains) and people have voted
with their feet: we now have many uses of [] {} in Qt already.
Thanks,
Marc
--
Marc Mutz
Principal Software Engineer
The Qt Company
Erich-Thilo-Str. 10 12489
Berlin, Germany
www.qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht Charlottenburg,
HRB 144331 B
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
