Start with the following code: class Foo { Foo(); }; Foo::Foo() { ; } Wait for parsing to finish and everything to get highlighted. Now add a space(!) after the constructor's definition prototype: Foo::Foo() <-- add a space here { ; } The modified line is now underlined in red, and the tooltip shows "Problem in Semantic analysis: Adapt Signature" and offers to "Update declaration signature", even though there was no actual change to the signature. (Selecting this solution then triggers bug 375276 and makes the code invalid).
This also happens if you add another line of instantiation outside of the brackets. header: int bar; cpp file: class Foo: bar(0) { } adding the bar(0) will also do the update declaration signature thing.
Yes, that's where I noticed it initially; then I noticed a simple space was enough to trigger it.
I can confirm this.
Can't Reproduce I think fixed in commit https://phabricator.kde.org/R32:e334d754bf510bdf21368858d8494adf3622fb16
Sounds sane to me. Marking as duplicate. *** This bug has been marked as a duplicate of bug 365420 ***