1. 12 Sep, 2018 1 commit
  2. 20 Aug, 2018 1 commit
  3. 17 Aug, 2018 1 commit
  4. 15 Aug, 2018 3 commits
  5. 13 Aug, 2018 1 commit
  6. 06 Aug, 2018 1 commit
  7. 15 Mar, 2018 1 commit
  8. 01 Mar, 2018 1 commit
  9. 26 Feb, 2018 1 commit
  10. 09 Jan, 2018 4 commits
    • Milian Wolff's avatar
      Workaround: find declarations for constructor argument hints · 113deb25
      Milian Wolff authored
      For non-namespaced constructors we can find the declarations by
      manually adding the identifier a second time before the lookup,
      as that gives us the proper QID. This allows us to find the
      declaration for many situations, most notably for most Qt classes.
      Subscribers: kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D9745
    • Milian Wolff's avatar
      clang: Improve argument hint code completion · 203b02d4
      Milian Wolff authored
      Previously, the overload candidates never got an DUChain Declaration
      associated, meaning we could not inspect the API documentation in-line
      from the code completion. The reason was that most of the time the
      hinted declaration is also a valid "normal" completion item, and thus
      was found a second time. The findDeclaration call then returned null
      for the second call, since we added the declaration to the exclusion
      set after the first call. Instead, use a separate set for overload
      candidates to fix this. Note that the expanded argument hint item
      is still not showing any documentation in-line... Apparently there's
      more to fix to get this done properly.
      While at it, also use the ArgumentHintItem for the situations where
      we (now) find a Declaration, to get proper current-argument
      Then fix the unit test to expect the default arguments. Though
      potentially this is clang-version dependent? Anyhow, this makes the
      test pass for me on my machine with libclang from LLVM 5.0.0.
      Reviewers: #kdevelop
      Subscribers: kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D9725
    • Milian Wolff's avatar
      Cleanup: use auto and remove explicit KDevelop:: qualification from identifiers · f1f23ce1
      Milian Wolff authored
      Reviewers: #kdevelop
      Subscribers: kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D9721
    • Milian Wolff's avatar
      Cleanup: Reduce amount of ifdefs · 35d1bfa3
      Milian Wolff authored
      Only use one ifdef and store result in a boolean, then use that
      variable elsewhere.
      Reviewers: #kdevelop
      Subscribers: kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D9720
  11. 21 Nov, 2017 1 commit
  12. 28 Sep, 2017 1 commit
  13. 13 Sep, 2017 1 commit
  14. 29 Jul, 2017 4 commits
  15. 27 Jul, 2017 1 commit
    • Sven Brauch's avatar
      clang: fix precompiled preamble cache misses · f14a8fc9
      Sven Brauch authored
      We were a) passing in a wrong file size, and b) a different set of unsaved
      files on building the translation unit as compared to invoking completion.
      This resulted in the precompiled preamble being rebuilt every single time.
      On my test file, time spent in clang_codeCompleteAt goes down from ~700ms
      to ~12ms with this change after the project is fully parsed.
      It still doesn't work in header files at all.
      Differential Revision: https://phabricator.kde.org/D6905
  16. 16 Jul, 2017 1 commit
  17. 28 Jun, 2017 3 commits
  18. 07 Apr, 2017 1 commit
  19. 23 Mar, 2017 1 commit
  20. 04 Jan, 2017 1 commit
  21. 08 Sep, 2016 1 commit
  22. 23 Jul, 2016 1 commit
  23. 09 Jul, 2016 1 commit
  24. 14 Jan, 2016 2 commits
    • Milian Wolff's avatar
      Filter out declarations that don't belong to the clang plugin. · 25fafab4
      Milian Wolff authored
      Not sure what would happen if we'd get declarations from other
      languages in the clang code completion... I don't want to know.
      So better be safe and filter out all other languages.
    • Kevin Funk's avatar
      Clang: Fix crash in findDeclaration · b2291e2a
      Kevin Funk authored
      This happens when KDevelop tries to load stale declarations, e.g. from
      an unloaded language plugin.
      See message:
      [kdevelop(21511)/(kdevplatform.language) unknown(0): Cannot load a
      top-context from file
      - the required language-support for handling ID 100 is probably not
      [kdevelop(21511)/(kdevelop.plugins.clang) unknown(0): Detected an
      invalid declaration for "acos"
      ^ That last line was added as part of this patch.
      0  KDevelop::Declaration::kind (this=0x0) at
      1  0x00007fffc2f26ef4 in (anonymous namespace)::findDeclaration
      (qid=..., ctx=..., position=..., handled=Python Exception <class
      'gdb.error'> There is no member named next.:
      ) at
      2  0x00007fffc2f2534e in ClangCodeCompletionContext::completionItems
      (this=0x7fffa4003e40, abort=@0x7fffb2def7a8: false) at
      3  0x00007fffc2f22729 in (anonymous
      (this=0x3e72ed0, url=..., position=..., text=..., followingText=...) at
  25. 17 Dec, 2015 1 commit
  26. 01 Dec, 2015 1 commit
  27. 10 Nov, 2015 2 commits
  28. 09 Nov, 2015 1 commit