Why is there one completion thread per completion model?

Milian Wolff mail at milianw.de
Mon Sep 27 12:00:03 UTC 2010

Hello all,

got one of my "why is XYZ done this way" questions again. Often our KDevelop 
backtraces are immensely huge since we have lots of threads. One of the thins 
I noticed that each CodeCompletionModel (we have one per language plugin at 
least) will start its own CodeCompletionThread. Isn't that obsolete?

Couldn't it be one thread for all? Or is this too complicated and having lots 
of threads no issue?

Milian Wolff
mail at milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100927/e421b2cd/attachment.sig>

More information about the KDevelop-devel mailing list