11 Jan
2014
11 Jan
'14
6:03 p.m.
So basically you suggest to require the filesystem implementation concept to be able to work with boost::filestystem::path, but not restrain using a more filesystem-specific version of path, if it makes sense for this filesystem. boost::filesystem::path would just be the default path type, but not the only one usable depending on the filesystem implementation. Did I understand correctly? Also, what is your intent with the draft exactly? Do you want to provide such modifications? (as a PR maybe?) Or are you asking the maintainer to do it because you don't feel that you can yourself?