1. 18 Sep, 2020 2 commits
  2. 17 Sep, 2020 1 commit
  3. 09 Sep, 2020 3 commits
  4. 07 Sep, 2020 4 commits
  5. 05 Sep, 2020 1 commit
  6. 03 Sep, 2020 3 commits
  7. 02 Sep, 2020 2 commits
    • Igor Kushnir's avatar
      Don't crash during a slow (>= 60 seconds) startup · 43db1a72
      Igor Kushnir authored
      A quick benchmark shows that the added QCoreApplication::processEvents()
      call takes the same time - 6 milliseconds - in Debug and Release builds.
      6 milliseconds is not a noticeable startup slowdown, especially
      considering that the event loop does useful work: processes events,
      which would have to be handled eventually anyway.
      
      BUG: 425841
      FIXED-IN: 5.7.0
      43db1a72
    • Igor Kushnir's avatar
      Remove a duplicate qCWarning(SHELL) · 817be892
      Igor Kushnir authored
      355124b2 (master branch) upper-cased the
      first letter of this warning. bda72ef1
      (branch 5.1) switched from qWarning() to qCWarning(SHELL).
      33f15abf merged 5.1 into master, but
      ended up including two almost identical warnings. This commit removes
      the warning that starts with a lower-case letter.
      817be892
  8. 01 Sep, 2020 1 commit
  9. 31 Aug, 2020 3 commits
  10. 30 Aug, 2020 1 commit
  11. 29 Aug, 2020 1 commit
  12. 28 Aug, 2020 2 commits
  13. 27 Aug, 2020 1 commit
  14. 26 Aug, 2020 1 commit
  15. 24 Aug, 2020 2 commits
  16. 23 Aug, 2020 2 commits
  17. 22 Aug, 2020 1 commit
  18. 18 Aug, 2020 1 commit
    • Igor Kushnir's avatar
      Remove unneeded uses of 'volatile' · 1d059dee
      Igor Kushnir authored
      I have analyzed the current code and the commits that introduced these
      'volatile' uses. Nothing seems even close to actually warrant volatile.
      I can think of 3 reasons why it was introduced in the first place:
      
        1. (most likely) temporary debugging/testing use that became permanent
           by oversight;
        2. some esoteric compiler/optimizer bug workaround (this hypothetical
           bug is highly unlikely to have survived for more than 10 years to
           remain in GCC);
        3. a way to work around / hide a bug in the code itself (unlikely;
           this would be an unreliable fix that could break with any compiler
           update or a different compiler).
      
      'volatile' is used very sparingly in KDevelop code because it is very
      rarely useful in application code. See also
      http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1152r0.html
      for valid 'volatile' use cases.
      
      test_codecompletion, test_duchain and test_embeddedfreetree still pass
      with these changes.
      1d059dee
  19. 17 Aug, 2020 4 commits
  20. 16 Aug, 2020 4 commits