Things To Look Out For In Reviews: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Start section on new classes)
m (Fix internal links)
Line 1: Line 1:
[[Category:Developing_Qt::Guidelines]]
[[Category:Developing_Qt::Guidelines]]


This page is a low-entry-bar staging area for potential project-wide guidelines. After each release, we should go over each of these and decide whether we keep them here, or, preferably, fold them into [API Design Principles], [Qt Coding Style], [Coding Conventions] or a new or existing QUIP.
This page is a low-entry-bar staging area for potential project-wide guidelines. After each release, we should go over each of these and decide whether we keep them here, or, preferably, fold them into [[API Design Principles]], [[Qt Coding Style]], [[Coding Conventions]] or a new or existing QUIP.


= Newly-Added Things =
= Newly-Added Things =

Revision as of 08:37, 5 January 2024


This page is a low-entry-bar staging area for potential project-wide guidelines. After each release, we should go over each of these and decide whether we keep them here, or, preferably, fold them into API Design Principles, Qt Coding Style, Coding Conventions or a new or existing QUIP.

Newly-Added Things

When adding a new Thing, don't forget to provide rationale.

Enums

New Classes

Make sure new classes follow the draft value-class mechanics QUIP-22.

Polymorphic Classes

- Make dtor out-of-line, even if empty (then =default it). Rationale: pins the vtable to a single TU (and prevents -Wweak-vtable warnings). References: https://bugreports.qt.io/browse/QTBUG-45582

Decided To Keep Here

(make a proper subsection grouping when moving stuff here)