> Any feedback? Which would be preferable type Path = distinct string or type > Path[FilesystemEntity, FilesystemLocality] = distinct string ?
My solution which uses 4 distinct types would still be preferable to me ;-) However, if you want fewer types, at least distinguish between directories and files which have almost nothing in common. `openFile` cannot open directories and even if it could, what the heck would `readBytes` mean for a directory... I think the API that I use in the compiler works well and has been battle-tested as the compiler does a suprising amount of path manipulations. > After taking into account any feedback, would a sample implementation that > wraps current Standard Library functionality be desirable? Yes. There is one more missing aspect to this though, keeping paths as `string` (`distinct` or not does not matter for this point) is not optimal for the Windows target where Paths are in UTF-16 natively and so involve a translation step. This translation step is done repeatedly whereas otherwise it could be done only once.
