Hoogle Search

Within LTS Haskell 24.4 (ghc-9.10.2)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. FilePathHomeDir :: FilePathRoot

    cabal-install Distribution.Client.Glob

    No documentation available.

  2. FilePathRelative :: FilePathRoot

    cabal-install Distribution.Client.Glob

    No documentation available.

  3. data FilePathRoot

    cabal-install Distribution.Client.Glob

    No documentation available.

  4. FilePathRoot :: FilePath -> FilePathRoot

    cabal-install Distribution.Client.Glob

    e.g. "/", "c:" or result of takeDrive

  5. FilePathHomeDir :: FilePathRoot

    cabal-install Distribution.Client.RebuildMonad

    No documentation available.

  6. FilePathRelative :: FilePathRoot

    cabal-install Distribution.Client.RebuildMonad

    No documentation available.

  7. data FilePathRoot

    cabal-install Distribution.Client.RebuildMonad

    No documentation available.

  8. FilePathRoot :: FilePath -> FilePathRoot

    cabal-install Distribution.Client.RebuildMonad

    e.g. "/", "c:" or result of takeDrive

  9. fromFilePath :: FilePath -> IO ByteString

    bytestring Data.ByteString

    Convert a FilePath to a ByteString. The FilePath type is expected to use the file system encoding as reported by getFileSystemEncoding. This encoding allows for round-tripping of arbitrary data on platforms that allow arbitrary bytes in their paths. This conversion function does the same thing that openFile would do when decoding the FilePath. This function is in IO because the file system encoding can be changed. If the encoding can be assumed to be constant in your use case, you may invoke this function via unsafePerformIO.

  10. toFilePath :: ByteString -> IO FilePath

    bytestring Data.ByteString

    Convert a ByteString to a FilePath. This function uses the file system encoding, and resulting FilePaths can be safely used with standard IO functions and will reference the correct path in the presence of arbitrary non-UTF-8 encoded paths. This function is in IO because the file system encoding can be changed. If the encoding can be assumed to be constant in your use case, you may invoke this function via unsafePerformIO.

Page 11 of many | Previous | Next