[Differential] [Request, 20 lines] D2649: MissingIncludeAssistant: use the compilation unit as a path

[nicolaih (Nicolai Hähnle)]

nicolaih created this revision.
Restricted Application added a subscriber: kdevelop-devel.

REVISION SUMMARY
  For the purpose of determining where custom defines and includes should
  be added, the final location of the diagnostic is irrelevant: it's the
  path to the compilation unit itself that matters, since that's where the
  corresponding configuration is taken from.
  
  If you have a missing include file in an include file, compilationUnit()
  gives the path in which a custom include should be added, unlike
  finalLocation().

REPOSITORY
  rKDEVELOP KDevelop

BRANCH
  pub-includes1-compilation-unit

REVISION DETAIL
  https://phabricator.kde.org/D2649

AFFECTED FILES
  languages/clang/duchain/clangproblem.cpp
  languages/clang/duchain/clangproblem.h
  languages/clang/duchain/missingincludepathproblem.cpp

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: nicolaih
Cc: kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160904/634654b1/attachment.html>