diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-26 20:17:50 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-26 20:17:50 +0200 |
| commit | 9c782e0c96c19525babc6c7ceb4f1a184a400169 (patch) | |
| tree | c8bb73d446287bedff1fb13660e147cec5bc42ee /src/pendingchangesdialog.cpp | |
| parent | 494e2f263831614f3ea4f023ba93ccc7d740e0c1 (diff) | |
| download | qtmaildir-9c782e0c96c19525babc6c7ceb4f1a184a400169.tar.gz qtmaildir-9c782e0c96c19525babc6c7ceb4f1a184a400169.zip | |
The status rows for 119 and its duplicate 146, 119's section moved to the
closed file on this commit rather than left for a later cleanup, and the
README and changelog entries for the feature.
CLAUDE.md gains three findings, all of which cost time to learn here:
A defensive counter for an unreachable case is worse than nothing, because
it blocks the feature that needs the data. Reading the code said that branch
was reachable and the reading was wrong; instrumenting it and running the
suite is what settled it, and the tests that appeared to exercise it were
driving it from outside the production path.
PendingChangesDialog groups by a run rather than a map, which is why the
snapshot is stable-sorted, and startsMessage is carried rather than inferred
so a stale row still opens its own run.
A queued call carrying a container deserves the same suspicion as a Q_ENUM,
with the measurement: both containers cross intact on Qt 6.11, but a
standalone probe found QMetaType::fromName("QList<int>") invalid while
QList<bool> resolved, so the property does not follow from the type.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P88Q3MCSCSQxKDy7pmXh9F
Diffstat (limited to 'src/pendingchangesdialog.cpp')
0 files changed, 0 insertions, 0 deletions
