<table><tr><td style="">ahmadsamir added inline comments.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D23813">View Revision</a></tr></table><br /><div><strong>INLINE COMMENTS</strong><div><div style="margin: 6px 0 12px 0;"><div style="border: 1px solid #C7CCD9; border-radius: 3px;"><div style="padding: 0; background: #F7F7F7; border-color: #e3e4e8; border-style: solid; border-width: 0 0 1px 0; margin: 0;"><div style="color: #74777d; background: #eff2f4; padding: 6px 8px; overflow: hidden;"><a style="float: right; text-decoration: none;" href="https://phabricator.kde.org/D23813#inline-135136">View Inline</a><span style="color: #4b4d51; font-weight: bold;">kossebau</span> wrote in <span style="color: #4b4d51; font-weight: bold;">kkeysequencewidget.cpp:127</span></div>
<div style="margin: 8px 0; padding: 0 12px; color: #74777D;"><p style="padding: 0; margin: 8px;">Still unsure what you mean with the constness, as the QHash <tt style="background: #ebebeb; font-size: 13px;">shortcuts</tt> has been const all the time, and thus the access methods and its returned references. If you meant the initially proposed <tt style="background: #ebebeb; font-size: 13px;">const QKeySequence &seq = it.key();</tt> that was just an alias reference to something const ref before (<tt style="background: #ebebeb; font-size: 13px;">it.key()</tt>), whose idea was to not touch the other existing code as well as make it more obvious to the code reader what <tt style="background: #ebebeb; font-size: 13px;">it.key()</tt> is. It did not change any constness.</p>
<p style="padding: 0; margin: 8px;">Back to your original comment:<br />
So here my 2 penny collected over decades: avoid that. One change/aspect at a time. No additional clean-up., as basic as it is (even no whitespace changes, unless line touched anyway).</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">The commit message might miss to mention that change, or make it more complicated to read because it lists all the while-at-it changes.</li>
<li class="remarkup-list-item">There are no obvious changes, unless documented. What is clear to the commit creator, might be unclear to the commit reader, as they have another context</li>
<li class="remarkup-list-item">Line-wise commit annotation mark-up will be set for lines which are changed while not relevant for the actual main change (which only would be mentioned in the commit message first line/title)</li>
<li class="remarkup-list-item">One is concentrated on the main change, and might miss important details relevant to that other change, and introduce regressions.</li>
</ul>
<p style="padding: 0; margin: 8px;">You may discard these 2 penny of mine, but let's talk again in some years ;) Better though ask the search engine for what other people recommend as best commit practice & compare. Still you are free to collect your own experience: if young people only did what old people tell them, new discoveries would never be made ;) But most of the times...</p></div></div>
<div style="margin: 8px 0; padding: 0 12px;"><p style="padding: 0; margin: 8px;">I do try to keep commits atomic, and detail my changes in the commit message. (And no, I won't discard your 2 pennies, I am too poor, experience-wise, to afford that). What I should have done was read the code starting at the top, where shortcuts is declared const. Anyway thanks for explaining things, that's always appreciated. :)</p></div></div></div></div></div><br /><div><strong>REPOSITORY</strong><div><div>R263 KXmlGui</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D23813">https://phabricator.kde.org/D23813</a></div></div><br /><div><strong>To: </strong>kossebau, dfaure<br /><strong>Cc: </strong>ahmadsamir, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, bruns<br /></div>