Review Request 122164: Cache custom includes in main thread

[Milian Wolff]

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



duchain/helpers.cpp
<https://git.reviewboard.kde.org/r/122164/#comment51606>

    here you also probably want to pass the enumerator to tell the IDAIM that you are only interested in custom include paths, not C++ compiler paths



pythonparsejob.cpp
<https://git.reviewboard.kde.org/r/122164/#comment51605>

    I suggest you store the data here in a member variable and use that then in the ::run method. That way, you don't need any mutex.


- Milian Wolff


On Jan. 20, 2015, 8:10 a.m., Radek Novacek wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/122164/
> -----------------------------------------------------------
> 
> (Updated Jan. 20, 2015, 8:10 a.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Repository: kdev-python
> 
> 
> Description
> -------
> 
> Custom includes can't be obtained in the background thread, we must
> cache it from main thread.
> 
> 
> Diffs
> -----
> 
>   duchain/helpers.h d0212414a7c6dbf2a3bf251216632673d7fb32bd 
>   duchain/helpers.cpp a252d7cccac9aa1f563f5539060a071e88ced9c9 
>   pythonparsejob.cpp cc50eebfa3fd75817010ff70fcd4f621cbe89346 
> 
> Diff: https://git.reviewboard.kde.org/r/122164/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Radek Novacek
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20150120/1ff83b19/attachment-0001.html>