[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 Igor Kushnir changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #9 from Bug Janitor

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #8 from Igor Kushnir --- (In reply to Alessandro Carinelli from comment #5) > I had an idea: after we get trimmedText we move backwards starting from the > character right before the '.' checking every character until we find > something dif

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #7 from Igor Kushnir --- When I apply the attached patch, I get the following output while reproducing the bug: RESULTS: 1 ; kind: OverloadCandidate kind: 2 chunk text: "Test" kind: 10 chunk text: "{" kind: 3 chunk text: "int a" kind: 14 chu

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #6 from Igor Kushnir --- Created attachment 158431 --> https://bugs.kde.org/attachment.cgi?id=158431&action=edit Patch to print completion info and assist in investigation -- You are receiving this mail because: You are watching all bug

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #5 from Alessandro Carinelli --- Thanks for the help. Unfortunately both clang_getDiagnosticCategoryText and clang_getDiagnosticSpelling seem to return empty strings in this case (while in the case of a floating point literal with a leading

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #4 from Igor Kushnir --- Also take a look at related functions in include/clang-c/CXDiagnostic.h (or include/clang-c/Index.h). For example, I think clang_getDiagnosticSpelling() can potentially clarify the meaning of the single completion re

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #3 from Igor Kushnir --- (In reply to Alessandro Carinelli from comment #2) > Checking that m_results->Numresults is also different from 1 on line 984 > seems to fix the issue but I have no idea about what this variable > represents and I fo

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #2 from Alessandro Carinelli --- The substitution in object happens at line 1000 in file plugins/clang/codecompletion/context.cpp, before that (line 984) the value of m_results->NumResults is checked to be different from 0. I noticed that in

[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization

https://bugs.kde.org/show_bug.cgi?id=468605 Igor Kushnir changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0