Bug 385217 - code completion gives foo:foo::foo() instead of foo:foo()
Summary: code completion gives foo:foo::foo() instead of foo:foo()
Status: RESOLVED DUPLICATE of bug 384710
Alias: None
Product: kdevelop
Classification: Applications
Component: Code completion (other bugs)
Version First Reported In: git master
Platform: Compiled Sources All
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-29 20:22 UTC by RJVB
Modified: 2018-10-19 16:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2017-09-29 20:22:49 UTC
The code completion has had a feature for a while where you could start entering an out-of-line class method implementation and it would propose an appropriate completion. For instance when foo.h contains the declaration for a new ctor foo(QObject *parent), it would propose to complete to `foo::foo(QObject *parent)` after typing just foo: on the start of a new line.

That still happens, but now the completion doesn't remove the original ext anymore, so one ends up with `foo::foo::foo(QObject *parent)` (or foo:foo::foo(QObject *parent)). A pity, it's almost faster to type the whole thing by hand than correcting the completion result.
Comment 1 RJVB 2017-09-29 20:48:20 UTC
Or worse:

void AbstractFileManagerPlugin::addDirToWatcher( void KDevelop::AbstractFileManagerPlugin::addDirToWatcher(KDevelop::ProjectWatcher* watcher, const QString& path)

I had typed "void AbstractFileManagerPlugin::addDirToWatcher(" before the parser realised it had something to propose ...
Comment 2 Amish Naidu 2018-10-19 16:56:22 UTC

*** This bug has been marked as a duplicate of bug 384710 ***