Path is:module
A collection of FFI declarations for interfacing with Win32.
A collection of FFI declarations for interfacing with Win32.
A collection of FFI declarations for interfacing with Win32.
This module provides various helpful utilities for dealing with path
and file names, directories, and related support.
Written by John Goerzen, jgoerzen@complete.org
This library provides a well-typed representation of paths in a
filesystem directory tree.
Both
Path.Posix and
Path.Windows provide the same
interface. This module will reexport the appropriate module for your
platform.
High‐level, byte‐based file and directory path manipulations. You
probably want to import
Filesystem.Path.CurrentOS instead,
since it handles detecting which rules to use in the current
compilation.
This module defines
paths, which are collections of concretely
located
Trails. Many drawing systems (cairo, svg, ...) have a
similar notion of "path". Note that paths with multiple trails are
necessary for being able to draw
e.g. filled objects with holes
in them.
Paths in two dimensions are special since we may stroke them to create
a 2D diagram, and (eventually) perform operations such as intersection
and union. They also have a trace, whereas paths in higher dimensions
do not.
No description available in the introspection data.
Well typed and flexible file systems paths, preserving the OS and
filesystem encoding.
You can choose the level of type safety you want.
Path is the
basic path type which can represent a file, directory, absolute or
relative path with no restrictions. Depending on how much type safety
you want you can choose appropriate type wrappers to wrap
Path.
File Path mandates the path to be a file whereas
Abs
(File Path) mandates it to be an absolute path representing a
file.
You can upgrade or downgrade the safety. Whenever a less restrictive
path type is converted to a more restrctive path type the conversion
involves checks and it may fail. However, a more restrictive path type
can be freely converted to a less restrictive one.
See the
streamly-filepath package for interworking with the
OsPath type. The
Path type can be converted to and
from
OsPath type at zero cost since the underlying
representation of both is the same.
Find the location of the local Hackage database that is maintained by
running cabal update.
Utility functions to help create SVG path attributes, and transforms.
A more type-safe version of file paths
This module is intended to replace imports of System.FilePath, and
additionally exports thin wrappers around common IO functions. To
facilitate importing this module unqualified we also re-export some
definitions from System.IO (importing both would likely lead to name
clashes).
Note that his module does not import any other modules from
Hackage.Security; everywhere else we use Path instead of FilePath
directly.
Types and functions related to Stack's path command.