Review Request 117922: Preliminary implementation of adjust signature helper

Olivier Jean de Gaalon olivier.jg at gmail.com
Thu May 1 08:18:55 UTC 2014


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117922/#review57047
-----------------------------------------------------------


A few general points about this:
1. Regarding testing, have you seen languages/cpp/tests/test_cppassistants.cpp?
2. Wouldn't this overwrite any default arguments on the declaration?
3. This brings over the oldcpp StaticCodeAssistant more or less intact, whereas we are planning to make this part language agnostic.

One particular issue is that the sigassist should really behave a lot more like the rename assistant, which attaches to a view and manages its own usefulness much more accurately than sigassist is able to. We really don't want to go down the old route of creating a new SignatureAssistant each check. Ideally with the language agnostic StaticCodeAssistant, this sort of usefulness management will be codified.

Perhaps you could coordinate with Kevin Funk, who will be working on this as part of his GSOC project? Are you on #kdevelop (freenode)?

- Olivier Jean de Gaalon


On May 1, 2014, 5:08 a.m., David Stevens wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/117922/
> -----------------------------------------------------------
> 
> (Updated May 1, 2014, 5:08 a.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Repository: kdev-clang
> 
> 
> Description
> -------
> 
> This is a preliminary implementation of the adjust signature helper. It works fairly well under normal usage, but it runs into problems if the user starts trying to use it at a high frequency. There are some rather fundamental issues both due to the different information organization (files vs translation units) and due to the discrepencies between what KDevelop has in the text editor and what clang has in the translation units. Hopefully I can get some feedback on the implementation.
> 
> 
> Diffs
> -----
> 
>   clangsupport.h 1316f88 
>   clangsupport.cpp 5e3f464 
>   codecompletion/completionhelper.cpp dfaf6b3 
>   codegen/CMakeLists.txt 0b913bd 
>   codegen/clangcodeassistant.h PRE-CREATION 
>   codegen/clangcodeassistant.cpp PRE-CREATION 
>   codegen/clangsignatureassistant.h PRE-CREATION 
>   codegen/clangsignatureassistant.cpp PRE-CREATION 
>   tests/CMakeLists.txt c2fd36d 
>   util/clangutils.h 3516821 
>   util/clangutils.cpp a74017c 
> 
> Diff: https://git.reviewboard.kde.org/r/117922/diff/
> 
> 
> Testing
> -------
> 
> Manual. Any unit tests would be deeply tied into the GUI, so I'm not sure how to go about writing those. The old c++ plugin unfortunately doesn't have any tests to work off of.
> 
> 
> Thanks,
> 
> David Stevens
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20140501/4fab925b/attachment.html>


More information about the KDevelop-devel mailing list