#12, note that this library helps move towards an abstract filepath type

haskell · Dec 22, 2015 · 10553c6 · 10553c6
1 parent a5518ec
commit 10553c6
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/README.md b/README.md
@@ -16,3 +16,4 @@ The answer for this library is "no". While an abstract `FilePath` has some advan
 * It is not immediately obvious what a `FilePath` is, and what is just a pure `String`. For example, `/path/file.ext` is a `FilePath`. Is `/`? `/path`? `path`? `file.ext`? `.ext`? `file`?
 * Often it is useful to represent invalid files, e.g. `/foo/*.txt` probably isn't an actual file, but a glob pattern. Other programs use `foo//bar` for globs, which is definitely not a file, but might want to be stored as a `FilePath`.
 * Some programs use syntactic non-semantic details of the `FilePath` to change their behaviour. For example, `foo`, `foo/` and `foo/.` are all similar, and refer to the same location on disk, but may behave differently when passed to command-line tools.
+* A useful step to introducing an abstract `FilePath` is to reduce the amount of manipulating `FilePath` values like lists. This library hopes to help in that effort.