hpath: Support for well-typed paths

[ bsd3, filesystem ] [ Propose Tags ]

Support for well-typed paths, utilizing ByteString under the hood.

[Skip to Readme]
Versions [faq] 0.5.9, 0.6.0, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.7.5, 0.8.0, 0.8.1, 0.9.0, 0.9.1, 0.9.2 (info)
Change log CHANGELOG
Dependencies base (>=4.6 && <5), bytestring (>=, deepseq, exceptions, hspec, IfElse, simple-sendfile (>=0.2.24), unbuildable (>1 && <1), unix (>=2.5), unix-bytestring, utf8-string, word8 [details]
License BSD-3-Clause
Copyright Julian Ospald 2016
Author Julian Ospald <hasufell@posteo.de>
Maintainer Julian Ospald <hasufell@posteo.de>
Category Filesystem
Source repo head: git clone https://github.com/hasufell/hpath
Uploaded by maerwald at Thu Apr 12 00:38:35 UTC 2018
Distributions NixOS:0.9.2
Downloads 3643 total (80 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2018-04-13 [all 1 reports]




Maintainer's Corner

For package maintainers and hackage trustees

Readme for hpath-0.9.2

[back to package description]


Gitter chat Hackage version Build Status

Support for well-typed paths in Haskell. Also provides ByteString based filepath manipulation.


The motivation came during development of hsfm which has a pretty strict File type, but lacks a strict Path type, e.g. for user input.

The library that came closest to my needs was path, but the API turned out to be oddly complicated for my use case, so I decided to fork it.

Similarly, posix-paths was exactly what I wanted for the low-level operations, but upstream seems dead, so it is forked as well and merged into this library.


  • well-typed paths
  • high-level API to file operations like recursive directory copy
  • safe filepath manipulation, never using String as filepath, but ByteString
  • still allowing sufficient control to interact with the underlying low-level calls

Note: this library was written for posix systems and it will probably not support other systems.

Differences to 'path'

  • doesn't attempt to fake IO-related information into the path, so whether a path points to a file or directory is up to your IO-code to decide...
  • trailing path separators will be preserved if they exist, no messing with that
  • uses safe ByteString for filepaths under the hood instead of unsafe String
  • fixes broken dirname
  • renames dirname/filename to basename/dirname to match the POSIX shell functions
  • introduces a new Path Fn for safe filename guarantees and a RelC class
  • allows pattern matching via unidirectional PatternSynonym
  • uses simple doctest for testing
  • allows ~/ as relative path, because on posix level ~ is just a regular filename that does NOT point to $HOME
  • remove TH, it sucks

Differences to 'posix-paths'

  • uses the word8 package for save word8 literals instead of OverloadedStrings
  • hasTrailingPathSeparator and dropTrailingPathSeparator behave in the same way as their System.FilePath counterpart
  • added various functions:
    • equalFilePath
    • getSearchPath
    • hasParentDir
    • hiddenFile
    • isFileName
    • isValid
    • makeRelative
    • makeValid
    • normalise
    • splitSearchPath
    • stripExtension
  • has a custom versions of openFd which allows more control over the flags than its unix package counterpart
  • adds a getDirectoryContents' version that works on Fd

Examples in ghci

Start ghci via cabal repl:

-- enable OverloadedStrings
:set -XOverloadedStrings
-- import HPath.IO
import HPath.IO
-- parse an absolute path
abspath <- parseAbs "/home"
-- parse a relative path (e.g. user users home directory)
relpath <- parseRel "jule"
-- concatenate paths
let newpath = abspath </> relpath
-- get file type
getFileType newpath
-- return all contents of that directory
getDirsFiles newpath
-- return all contents of the parent directory
getDirsFiles (dirname newpath)