diff options
author | Nikolai Kosjar <nikolai.kosjar@theqtcompany.com> | 2016-01-11 15:20:04 +0100 |
---|---|---|
committer | Nikolai Kosjar <nikolai.kosjar@theqtcompany.com> | 2016-01-19 13:20:35 +0000 |
commit | 8d6549fa74bcc5e05f43497aef73e814a268139e (patch) | |
tree | 97abf08ec9c8cb02c102ce6a8a911d567b8472c7 /src/plugins/cpptools/cppheadersource_test.cpp | |
parent | 43800a6aa8111550ce6d0c4992c09bb657ef234e (diff) | |
download | qt-creator-8d6549fa74bcc5e05f43497aef73e814a268139e.tar.gz |
Clang: Correct member access operator if possible
1 struct Foo { int member; };
2 void f(Foo *foo)
3 {
4 foo.<REQUEST COMPLETION> // correct '.' to '->' and provide results
5 }
The preferred approach would be to check if "foo" in line 4 is of
pointer type, but there is no suitable cursor (only CompoundStmt) at
that position since the code is usually not yet parsed and thus invalid.
Thus, just run the completion as is. If there are not any results for a
dot completion, re-run the completion with "." exchanged by "->". This
approach is inherently slower than the preferred approach implemented in
the built-in code model.
The following rare cases are not handled:
1) Requesting completion after white space:
Works: foo.<COMPLETE HERE>
Fails: foo. <COMPLETE HERE>
2) Opening a file and requesting completion (ctrl+space) without prior
editing. No editing before triggering completion means that no
unsaved file is generated on the backend side, which is a
requirement for the correction.
Task-number: QTCREATORBUG-11581
Change-Id: I6bc8e8594778774ab342755fdb01a8a3e5c52ba0
Reviewed-by: Marco Bubke <marco.bubke@theqtcompany.com>
Diffstat (limited to 'src/plugins/cpptools/cppheadersource_test.cpp')
0 files changed, 0 insertions, 0 deletions