D7952: [WIP] make KDevelop::Path work with canonical representations

[René J.V. Bertin]

rjvbb added a comment.


  Why push for downstreaming here, forcing users to duplicate a feature that could (should, IMHO) be provided by Path? Why would a method like the proposed one that generates the canonical path NOT be at its place in Path?
  
  I didn't really mean to suggest that Path should always and exclusively work with canonical paths. Indeed it cannot know when it should canonicalise. Or rather, when it shouldn't. Maybe Path should indeed NOT convert the paths internally but only provide an option to canonicalise local paths on output.
  
  R.

REPOSITORY
  R32 KDevelop

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

To: rjvbb, #kdevelop, mwolff
Cc: mwolff, kdevelop-devel, geetamc, Pilzschaf, akshaydeo, surgenight, arrowdodger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170926/3339350a/attachment.html>