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.

Exact lookup

1. toFilePath :: Path b t -> FilePath

   path	Path.Internal.Posix

   Convert to a FilePath type. All directories have a trailing slash, so if you want no trailing slash, you can use dropTrailingPathSeparator from the filepath package.

2. toFilePath :: Path b t -> FilePath

   path	Path.Internal.Windows

   Convert to a FilePath type. All directories have a trailing slash, so if you want no trailing slash, you can use dropTrailingPathSeparator from the filepath package.

3. toFilePath :: Path b t -> FilePath

   path	Path.Posix

   Convert to a FilePath type. All directories have a trailing slash, so if you want no trailing slash, you can use dropTrailingPathSeparator from the filepath package.

4. toFilePath :: Path b t -> FilePath

   path	Path.Windows

   Convert to a FilePath type. All directories have a trailing slash, so if you want no trailing slash, you can use dropTrailingPathSeparator from the filepath package.

5. fromFilePath :: FilePath -> IO ByteString

   rio	RIO.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.

6. toFilePath :: ByteString -> IO FilePath

   rio	RIO.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.

7. equalFilePath :: FilePath -> FilePath -> Bool

   rio	RIO.FilePath

   Equality of two FILEPATHs. If you call System.Directory.canonicalizePath first this has a much better chance of working. Note that this doesn't follow symlinks or DOSNAM~1s. Similar to normalise, this does not expand "..", because of symlinks.

   x == y ==> equalFilePath x y
   normalise x == normalise y ==> equalFilePath x y
   equalFilePath "foo" "foo/"
   not (equalFilePath "/a/../c" "/c")
   not (equalFilePath "foo" "/foo")
   Posix:   not (equalFilePath "foo" "FOO")
   Windows: equalFilePath "foo" "FOO"
   Windows: not (equalFilePath "C:" "C:/")
   

8. getFilePathNT :: FilePathNT -> String

   Cabal-syntax	Distribution.FieldGrammar.Newtypes

   No documentation available.

9. PWTEmptyFilePath :: PWarnType

   Cabal-syntax	Distribution.Fields

   Empty filepath, i.e. literally ""

10. toFilePath :: ModuleName -> FilePath

    Cabal-syntax	Distribution.ModuleName

    Convert a module name to a file path, but without any file extension. For example:

    toFilePath (fromString "A.B.C") = "A/B/C"
    

Page 16 of many | Previous | Next