Review Request: Further improve auto-completion in switch statements.

[Ivan Shapovalov]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/105561/
-----------------------------------------------------------

(Updated July 16, 2012, 8:37 a.m.)


Review request for KDevelop and Olivier Jean de Gaalon.


Changes
-------

Changed nested-conditionals to multiple logic operators; cleared a debug statement.


Description
-------

Only compile-time integral constants are valid in "case ..."
statements, so filter any certainly non-constant completion items.

This has 2 usability issues (well, not issues, but questionable points):
1) We do not filter type-names since they can be used either as scopes
(SomeType::someConstant) or as ctor-like initializers
(SomeIntegralTypedef(42)).
2) We do not filter integer-returning functions since they
can be constexpr (thus syntactically usable) but we cannot handle
constexpr now.

But, since one rarely would use these items, their match quality
is forced to zero in order to avoid pollution of "best matches".


Diffs (updated)
-----

  languages/cpp/codecompletion/context.h e17fe7c 
  languages/cpp/codecompletion/context.cpp 34bc728 
  languages/cpp/tests/test_cppcodecompletion.h f88eb01 
  languages/cpp/tests/test_cppcodecompletion.cpp eb44618 

Diff: http://git.reviewboard.kde.org/r/105561/diff/


Testing
-------

Unit-tests have been made aware of the newly-introduced filtering (+ added a new unit-test verifying the filtering itself); usability has been discussed with Olivier Jean de Gaalon.


Thanks,

Ivan Shapovalov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20120716/980759e6/attachment.html>