h*      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`a1.8.2 2016@present Mark Karpov BSD 3 clause$Mark Karpov  experimentalportable Safe-Inferredpath-ioClass of things (bs) that can be canonicalized, made absolute, and made relative to a some base directory.path-io&Type of absolute version of the given path.path-io&Type of relative version of the given path.path-ioMake a path absolute and remove as many indirections from it as possible. Indirections include the two special directories . and .., as well as any symbolic links. The input path need not point to an existing file or directory.Note,: if you require only an absolute path, use  instead. Most programs need not care about whether a path contains symbolic links.Due to the fact that symbolic links are dependent on the state of the existing filesystem, the function can only make a conservative, best-effort attempt. Nevertheless, if the input path points to an existing file or directory, then the output path shall also point to the same file or directory.Formally, symbolic links are removed from the longest prefix of the path that still points to an existing file. The function is not atomic, therefore concurrent changes in the filesystem may lead to incorrect results.(Despite the name, the function does not guarantee canonicity of the returned path due to the presence of hard links, mount points, etc.) Known bug(s)<: on Windows, the function does not resolve symbolic links./Please note that before version 1.2.3.0 of the  directory package, this function had unpredictable behavior on non-existent paths.path-ioMake a path absolute by prepending the current directory (if it isn't already absolute) and applying c to the result.If the path is already absolute, the operation never fails. Otherwise, the operation may fail with the same exceptions as ..path-io*Make a path relative to a given directory.path-io2Make a path relative to current working directory.path-ioAction returned by the traversal handler function. The action controls how the traversal will proceed.Note : in version 1.4.0# the type was adjusted to have the b type parameter.path-io!Finish the entire walk altogetherpath-io3List of sub-directories to exclude from descendingpath-io dir creates a new directory dir which is initially empty, or as near to empty as the operating system allows.The operation may fail with:isPermissionError / PermissionDenied The process has insufficient privileges to perform the operation. [EROFS, EACCES]isAlreadyExistsError /  AlreadyExists: The operand refers to a directory that already exists.  [EEXIST] HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument. The operand is not a valid directory name. [ENAMETOOLONG, ELOOP] NoSuchThing& There is no path to the directory. [ENOENT, ENOTDIR]ResourceExhausted Insufficient resources (virtual memory, process file descriptors, physical disk space, etc.) are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]InappropriateType8 The path refers to an existing non-directory object. [EEXIST]path-io parents dir creates a new directory dir0 if it doesn't exist. If the first argument is d the function will also create all parent directories if they are missing.path-ioEnsure that a directory exists creating it and its parent directories if necessary. This is just a handy shortcut: #ensureDir = createDirIfMissing Truepath-io dir removes an existing directory dir. The implementation may specify additional constraints which must be satisfied before a directory can be removed (e.g. the directory has to be empty, or may not be in use by other processes). It is not legal for an implementation to partially remove a directory unless the entire directory is removed. A conformant implementation need not support directory removal in all situations (e.g. removal of the root directory).The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument. The operand is not a valid directory name. [ENAMETOOLONG, ELOOP]e /  NoSuchThing! The directory does not exist. [ENOENT, ENOTDIR]isPermissionError / PermissionDenied The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]UnsatisfiedConstraints; Implementation-dependent constraints are not satisfied. [EBUSY, ENOTEMPTY, EEXIST]UnsupportedOperation The implementation does not support removal in this situation. [EINVAL]InappropriateType; The operand refers to an existing non-directory object.  [ENOTDIR] path-io  dir removes an existing directory dir together with its contents and sub-directories. Within this directory, symbolic links are removed without affecting their targets.!path-ioRemove a file or directory at path together with its contents and subdirectories. Symbolic links are removed without affecting their targets. If the path does not exist, nothing happens.Unlike other removal functions, this function will also attempt to delete files marked as read-only or otherwise made unremovable due to permissions. As a result, if the removal is incomplete, the permissions or attributes on the remaining files may be altered. If there are hard links in the directory, then permissions on all related hard links may be altered.0If an entry within the directory vanishes while removePathForcibly% is running, it is silently ignored.0If an exception occurs while removing an entry, removePathForcibly will still try to remove as many entries as it can before failing with an exception. The first exception that it encountered is re-thrown."path-io" old new2 changes the name of an existing directory from old to new . If the new> directory already exists, it is atomically replaced by the old directory. If the new directory is neither the old directory nor an alias of the old% directory, it is removed as if by . A conformant implementation need not support renaming directories in all situations (e.g. renaming to an existing directory, or across different physical devices), but the constraints must be documented.On Win32 platforms,  renameDir fails if the new directory already exists.The operation may fail with: HardwareFault( A physical I/O error has occurred. [EIO]InvalidArgument3 Either operand is not a valid directory name. [ENAMETOOLONG, ELOOP]e /  NoSuchThing The original directory does not exist, or there is no path to the target. [ENOENT, ENOTDIR]isPermissionError / PermissionDenied The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]ResourceExhausted Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints= Implementation-dependent constraints are not satisfied. [EBUSY, ENOTEMPTY, EEXIST]UnsupportedOperation The implementation does not support renaming in this situation. [EINVAL, EXDEV]InappropriateType= Either path refers to an existing non-directory object. [ENOTDIR, EISDIR]#path-ioRename a file or directory. If the destination path already exists, it is replaced atomically. The destination path must not point to an existing directory. A conformant implementation need not support renaming files in all situations (e.g. renaming across different physical devices), but the constraints must be documented.The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument, Either operand is not a valid file name. [ENAMETOOLONG, ELOOP]e The original file does not exist, or there is no path to the target. [ENOENT, ENOTDIR]isPermissionError The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM] Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints; Implementation-dependent constraints are not satisfied. [EBUSY]UnsupportedOperation The implementation does not support renaming in this situation. [EXDEV]InappropriateType Either the destination path refers to an existing directory, or one of the parent segments in the destination path is not a directory. ,[ENOTDIR, EISDIR, EINVAL, EEXIST, ENOTEMPTY]$path-io$ dir returns a list of all entries in dir without the special entries (. and ..). Entries are not sorted.The operation may fail with: HardwareFault* A physical I/O error has occurred. [EIO]InvalidArgument2 The operand is not a valid directory name. [ENAMETOOLONG, ELOOP]e /  NoSuchThing% The directory does not exist. [ENOENT, ENOTDIR]isPermissionError / PermissionDenied The process has insufficient privileges to perform the operation. [EACCES]ResourceExhausted Insufficient resources are available to perform the operation. [EMFILE, ENFILE]InappropriateType< The path refers to an existing non-directory object.  [ENOTDIR]%path-io The same as $ but returns relative paths.&path-io Similar to $1, but recursively traverses every sub-directory excluding symbolic links, and returns all files and directories found. This can fail with the same exceptions as $.Note: before version 1.3.0", this function followed symlinks.'path-io The same as &= but returns paths that are relative to the given directory.(path-io#Copies a directory recursively. It does not follow symbolic links and preserves permissions when possible. If the destination directory already exists, new files and sub-directories complement its structure, possibly overwriting old files if they happen to have the same name as the new ones.Note: before version 1.3.0", this function followed symlinks.Note: before version 1.6.0, the function created empty directories in the destination directory when the source directory contained directory symlinks. The symlinked directories were not recursively traversed. It also copied symlinked files creating normal regular files in the target directory as the result. This was fixed in the version 1.6.00 so that the function now behaves much like the cp utility, not traversing symlinked directories, but recreating symlinks in the target directory according to their targets in the source directory.)path-io The same as ( , but it does not preserve directory permissions. This may be useful, for example, if the directory you want to copy is @read-only@, but you want your copy to be editable.Note: before version 1.3.0", this function followed symlinks.Note: before version 1.6.0, the function created empty directories in the destination directory when the source directory contained directory symlinks. The symlinked directories were not recursively traversed. It also copied symlinked files creating normal regular files in the target directory as the result. This was fixed in the version 1.6.00 so that the function now behaves much like the cp utility, not traversing symlinked directories, but recreating symlinks in the target directory according to their targets in the source directory.fpath-ioGeneric version of (. The first argument controls whether to preserve directory permissions or not. Does not+ follow symbolic links. Internal function.*path-ioTraverse a directory tree using depth first pre-order traversal, calling a handler function at each directory node traversed. The absolute paths of the parent directory, sub-directories and the files in the directory are provided as arguments to the handler.The function is capable of detecting and avoiding traversal loops in the directory tree. Note that the traversal follows symlinks by default, an appropriate traversal handler can be used to avoid that when necessary.+path-io The same as *0 but uses relative paths. The handler is given dir, directory relative to the directory where traversal begins. Sub-directories and files are relative to dir.,path-io Similar to * but accepts a g-returning output writer as well. Values returned by the output writer invocations are accumulated and returned.Both, the descend handler as well as the output writer can be used for side effects but keep in mind that the output writer runs before the descend handler.-path-io The same as ,< but uses relative paths. The handler and writer are given dir, directory relative to the directory where traversal begins. Sub-directories and files are relative to dir.hpath-ioNon-public helper function for defining accumulating walking actions..path-io9Obtain the current working directory as an absolute path.In a multithreaded program, the current working directory is a global state shared among all threads of the process. Therefore, when performing filesystem operations from multiple threads, it is highly recommended to use absolute rather than relative paths (see: ).The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]e or  NoSuchThing8 There is no path referring to the working directory. [EPERM, ENOENT, ESTALE...]isPermissionError or PermissionDenied The process has insufficient privileges to perform the operation. [EACCES]ResourceExhausted Insufficient resources are available to perform the operation.UnsupportedOperation The operating system has no notion of current working directory./path-io/Change the working directory to the given path.In a multithreaded program, the current working directory is a global state shared among all threads of the process. Therefore, when performing filesystem operations from multiple threads, it is highly recommended to use absolute rather than relative paths (see: ).The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument. The operand is not a valid directory name. [ENAMETOOLONG, ELOOP]e or  NoSuchThing! The directory does not exist. [ENOENT, ENOTDIR]isPermissionError or PermissionDenied The process has insufficient privileges to perform the operation. [EACCES]UnsupportedOperation The operating system has no notion of current working directory, or the working directory cannot be dynamically changed.InappropriateType8 The path refers to an existing non-directory object.  [ENOTDIR]0path-ioRun an i action with the given working directory and restore the original working directory afterwards, even if the given action fails due to an exception.3The operation may fail with the same exceptions as . and /.1path-io)Return the current user's home directory.The directory returned is expected to be writable by the current user, but note that it isn't generally considered good practice to store application-specific data here; use 2 instead. On Unix, 1 returns the value of the HOME environment variable. On Windows, the system is queried for a suitable path; a typical path might be  C:/Users/.The operation may fail with:UnsupportedOperation7 The operating system has no notion of home directory.e The home directory for the current user does not exist, or cannot be found.2path-ioObtain the path to a special directory for storing user-specific application data (traditional Unix location).The argument is usually the name of the application. Since it will be integrated into the path, it must consist of valid path characters."On Unix-like systems, the path is ~/..On Windows, the path is  %APPDATA%/ (e.g.  C:/Users//AppData/Roaming/)Note: the directory may not actually exist, in which case you would need to create it. It is expected that the parent directory exists and is writable.The operation may fail with:UnsupportedOperation The operating system has no notion of application-specific data directory.e The home directory for the current user does not exist, or cannot be found.3path-io-Return the current user's document directory.The directory returned is expected to be writable by the current user, but note that it isn't generally considered good practice to store application-specific data here; use 2 instead. On Unix, 3 returns the value of the HOME environment variable. On Windows, the system is queried for a suitable path; a typical path might be  C:/Users/ /Documents.The operation may fail with:UnsupportedOperation; The operating system has no notion of document directory.e The document directory for the current user does not exist, or cannot be found.4path-io1Return the current directory for temporary files. On Unix, 4 returns the value of the TMPDIR environment variable or "/tmp" if the variable isn't defined. On Windows, the function checks for the existence of environment variables in the following order and uses the first path found:TMP environment variable.TEMP environment variable.!USERPROFILE environment variable.The Windows directoryThe operation may fail with:UnsupportedOperation< The operating system has no notion of temporary directory.4The function doesn't verify whether the path exists.5path-ioObtain the paths to special directories for storing user-specific application data, configuration, and cache files, conforming to the  http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG Base Directory Specification. Compared with 2, this function provides a more fine-grained hierarchy as well as greater flexibility for the user.0It also works on Windows, although in that case  and  will map to the same directory.Note: The directory may not actually exist, in which case you would need to create it with file mode 700% (i.e. only accessible by the owner).Note also: this is a piece of conditional API, only available if directory-1.2.3.0 or later is used.6path-io Similar to 53 but retrieves the entire list of XDG directories. On Windows,  and  usually map to the same list of directories unless overridden.Refer to the docs of  for more details.7path-ioAppend stringly-typed path to an absolute path and then canonicalize it.8path-io The same as 7%, but uses current working directory.9path-io The same as 7, but for directories.:path-io The same as 9%, but uses current working directory.;path-io; file3 removes the directory entry for an existing file file, where file is not itself a directory. The implementation may specify additional constraints which must be satisfied before a file can be removed (e.g. the file may not be in use by other processes).The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument) The operand is not a valid file name. [ENAMETOOLONG, ELOOP]e /  NoSuchThing The file does not exist. [ENOENT, ENOTDIR]isPermissionError / PermissionDenied The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]UnsatisfiedConstraints; Implementation-dependent constraints are not satisfied. [EBUSY]InappropriateType0 The operand refers to an existing directory. [EPERM, EINVAL]<path-io< old new: changes the name of an existing file system object from old to new . If the new: object already exists, it is atomically replaced by the old object. Neither path may refer to an existing directory. A conformant implementation need not support renaming files in all situations (e.g. renaming across different physical devices), but the constraints must be documented.The operation may fail with: HardwareFault& A physical I/O error has occurred. [EIO]InvalidArgument, Either operand is not a valid file name. [ENAMETOOLONG, ELOOP]e /  NoSuchThing The original file does not exist, or there is no path to the target. [ENOENT, ENOTDIR]isPermissionError / PermissionDenied The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]ResourceExhausted Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints; Implementation-dependent constraints are not satisfied. [EBUSY]UnsupportedOperation The implementation does not support renaming in this situation. [EXDEV]InappropriateType0 Either path refers to an existing directory. ,[ENOTDIR, EISDIR, EINVAL, EEXIST, ENOTEMPTY]=path-io= old new copies the existing file from old to new . If the new7 file already exists, it is atomically replaced by the old file. Neither path may refer to an existing directory. The permissions of old are copied to new, if possible.>path-io#Obtain the size of a file in bytes.?path-ioGiven an executable file name, search for such file in the directories listed in system PATH=. The returned value is the path to the found executable or j if an executable with the given name was not found. For example (?" "ghc") gives you the path to GHC.The path returned by ?7 corresponds to the program that would be executed by  when passed the same string (as a RawCommand, not a ShellCommand). On Windows, ? calls the Win32 function  SearchPath, which may search other places before checking the directories in PATH. Where it actually searches depends on registry settings, but notably includes the directory containing the current executable. See  5http://msdn.microsoft.com/en-us/library/aa365527.aspx for more details.@path-io?Search through the given set of directories for the given file.Apath-ioSearch through the given set of directories for the given file and return a list of paths where the given file exists.Bpath-ioSearch through the given set of directories for the given file and with the given property (usually permissions) and return a list of paths where the given file exists and has the property.Cpath-io Create a file symbolic link. The target path can be either absolute or relative and need not refer to an existing file. The order of arguments follows the POSIX convention..To remove an existing file symbolic link, use ;.!Although the distinction between file symbolic links and  directory symbolic links does not exist on POSIX systems, on Windows this is an intrinsic property of every symbolic link and cannot be changed without recreating the link. A file symbolic link that actually points to a directory will fail to dereference and vice versa. Moreover, creating symbolic links on Windows may require privileges unavailable to users outside the Administrators group. Portable programs that use symbolic links should take both into consideration..On Windows, the function is implemented using CreateSymbolicLink. Since 1.3.3.0, the ,SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE flag is included if supported by the operating system. On POSIX, the function uses symlink and is therefore atomic.7Windows-specific errors: This operation may fail with  if the user lacks the privileges to create symbolic links. It may also fail with  5 if the file system does not support symbolic links.Dpath-io Create a  directory symbolic link. The target path can be either absolute or relative and need not refer to an existing directory. The order of arguments follows the POSIX convention.3To remove an existing directory symbolic link, use E.!Although the distinction between file symbolic links and  directory symbolic links does not exist on POSIX systems, on Windows this is an intrinsic property of every symbolic link and cannot be changed without recreating the link. A file symbolic link that actually points to a directory will fail to dereference and vice versa. Moreover, creating symbolic links on Windows may require privileges unavailable to users outside the Administrators group. Portable programs that use symbolic links should take both into consideration..On Windows, the function is implemented using CreateSymbolicLink with SYMBOLIC_LINK_FLAG_DIRECTORY. Since 1.3.3.0, the ,SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE flag is also included if supported by the operating system. On POSIX, this is an alias for C and is therefore atomic.7Windows-specific errors: This operation may fail with  if the user lacks the privileges to create symbolic links. It may also fail with  5 if the file system does not support symbolic links.Epath-ioRemove an existing  directory symbolic link.!On Windows, this is an alias for *. On POSIX systems, this is an alias for ;. See also: ;, which can remove an existing file symbolic link.Fpath-ioRetrieve the target path of either a file or directory symbolic link. The returned path may not exist, and may not even be a valid path.On Windows systems, this calls DeviceIoControl with FSCTL_GET_REPARSE_POINT. In addition to symbolic links, the function also works on junction points. On POSIX systems, this calls readlink.7Windows-specific errors: This operation may fail with  5 if the file system does not support symbolic links.Gpath-ioCheck whether the path refers to a symbolic link. An exception is thrown if the path does not exist or is inaccessible.On Windows, this checks for FILE_ATTRIBUTE_REPARSE_POINT. In addition to symbolic links, the function also returns true on junction points. On POSIX systems, this checks for S_IFLNK.+Check if the given path is a symbolic link.Hpath-io0Use a temporary file that doesn't already exist.Creates a new temporary file inside the given directory, making use of the template. The temporary file is deleted after use.Ipath-io%Create and use a temporary directory.Creates a new temporary directory inside the given directory, making use of the template. The temporary directory is deleted after use.Jpath-ioCreate and use a temporary file in the system standard temporary directory.Behaves exactly the same as H, except that the parent temporary directory will be that returned by 4.Kpath-ioCreate and use a temporary directory in the system standard temporary directory.Behaves exactly the same as I, except that the parent temporary directory will be that returned by 4.Lpath-io)The function creates a temporary file in rw mode. The created file isn't deleted automatically, so you need to delete it manually.The file is created with permissions such that only the current user can read/write it.With some exceptions (see below), the file will be created securely in the sense that an attacker should not be able to cause openTempFile to overwrite another file on the filesystem using your credentials, by putting symbolic links (on Unix) in the place where the temporary file is to be created. On Unix the O_CREAT and O_EXCL7 flags are used to prevent this attack, but note that O_EXCL is sometimes not supported on NFS filesystems, so if you rely on this behaviour it is best to use local filesystems only.Mpath-ioLike L, but opens the file in binary mode. On Windows, reading a file in text mode (which is the default) will translate CRLF to LF, and writing will translate LF to CRLF. This is usually what you want with text files. With binary files this is undesirable; also, as usual under Microsoft operating systems, text mode treats control-Z as EOF. Binary mode turns off all special treatment of end-of-line and end-of-file characters.Npath-ioCreate a temporary directory. The created directory isn't deleted automatically, so you need to delete it manually.The directory is created with permissions such that only the current user can read/write it.Opath-ioTest whether the given path points to an existing filesystem object. If the user lacks necessary permissions to search the parent directories, this function may return false even if the file does actually exist.Ppath-ioThe operation P returns d: if the argument file exists and is not a directory, and k otherwise.Qpath-ioThe operation Q returns d if the argument file exists and is either a directory or a symbolic link to a directory, and k otherwise.Rpath-io8Check if there is a file or directory on specified path.Spath-io&If argument of the function throws a  , j is returned (other exceptions propagate). Otherwise the result is returned inside a l.Tpath-io The same as S, but ignores result.Upath-ioThe U> operation returns the permissions for the file or directory.The operation may fail with:isPermissionError> if the user is not permitted to access the permissions; ore) if the file or directory does not exist.Vpath-ioThe V; operation sets the permissions for the file or directory.The operation may fail with:isPermissionError; if the user is not permitted to set the permissions; ore) if the file or directory does not exist.Wpath-ioSet permissions for the object found on second given path so they match permissions of the object on the first path.Xpath-ioObtain the time at which the file or directory was last accessed.The operation may fail with:isPermissionError< if the user is not permitted to read the access time; ore) if the file or directory does not exist.Caveat for POSIX systems: This function returns a timestamp with sub-second resolution only if this package is compiled against  unix-2.6.0.06 or later and the underlying filesystem supports them.=Note: this is a piece of conditional API, only available if directory-1.2.3.0 or later is used.Ypath-ioChange the time at which the file or directory was last accessed.The operation may fail with:isPermissionError= if the user is not permitted to alter the access time; ore) if the file or directory does not exist.Some caveats for POSIX systems:Not all systems support  utimensat, in which case the function can only emulate the behavior by reading the modification time and then setting both the access and modification times together. On systems where  utimensat is supported, the access time is set atomically with nanosecond precision.!If compiled against a version of unix prior to 2.7.0.0, the function would not be able to set timestamps with sub-second resolution. In this case, there would also be loss of precision in the modification time.=Note: this is a piece of conditional API, only available if directory-1.2.3.0 or later is used.Zpath-ioChange the time at which the file or directory was last modified.The operation may fail with:isPermissionError if the user is not permitted to alter the modification time; ore) if the file or directory does not exist.Some caveats for POSIX systems:Not all systems support  utimensat, in which case the function can only emulate the behavior by reading the access time and then setting both the access and modification times together. On systems where  utimensat is supported, the modification time is set atomically with nanosecond precision.!If compiled against a version of unix prior to 2.7.0.0, the function would not be able to set timestamps with sub-second resolution. In this case, there would also be loss of precision in the access time.=Note: this is a piece of conditional API, only available if directory-1.2.3.0 or later is used.[path-ioObtain the time at which the file or directory was last modified.The operation may fail with:isPermissionError if the user is not permitted to read the modification time; ore) if the file or directory does not exist.Caveat for POSIX systems: This function returns a timestamp with sub-second resolution only if this package is compiled against  unix-2.6.0.06 or later and the underlying filesystem supports them.mpath-ioLift an action in i that takes n< into an action in slightly more abstract monad that takes b.opath-io Similar to m but for functions with arity 2.ppath-io Similar to o;, but allows us to pass second argument of arbitrary type.qpath-ioLike r-, but also drops the trailing path separator.spath-io6Perform an action ignoring IO exceptions it may throw.\path-io]path-io,path-ioBase directorypath-io1Path that will be made relative to base directorypath-ioCreate its parents too?path-io*The path to the directory you want to make"path-ioOld namepath-ioNew name$path-ioDirectory to listpath-ioSub-directories and files%path-ioDirectory to listpath-ioSub-directories and files&path-ioDirectory to listpath-ioSub-directories and files'path-ioDirectory to listpath-ioSub-directories and files(path-ioSourcepath-io Destination)path-ioSourcepath-io Destinationfpath-io)Should we preserve directory permissions?path-ioSourcepath-io Destination*path-io Handler (dir -> subdirs -> files -> )path-io Directory where traversal begins+path-io Handler (dir -> subdirs -> files -> )path-io Directory where traversal begins,path-ioDescend handler (dir -> subdirs -> files -> %), descend the whole tree if omittedpath-ioOutput writer (dir -> subdirs -> files -> o)path-io Directory where traversal beginspath-ioAccumulation of outputs generated by the output writer invocations-path-ioDescend handler (dir -> subdirs -> files -> %), descend the whole tree if omittedpath-ioOutput writer (dir -> subdirs -> files -> o)path-io Directory where traversal beginspath-ioAccumulation of outputs generated by the output writer invocationshpath-ioThe walk function we usepath-ioDescend handler (dir -> subdirs -> files -> %), descend the whole tree if omittedpath-ioOutput writer (dir -> subdirs -> files -> o)path-io Directory where traversal beginspath-ioAccumulation of outputs generated by the output writer invocations0path-ioDirectory to execute inpath-ioAction to be executed2path-io/Name of application (used in path construction)5path-ioWhich special directorypath-io1A relative path that is appended to the path; if j, the base path is returned6path-ioWhich special directory list7path-ioBase directorypath-ioPath to resolve8path-ioPath to resolve9path-ioBase directorypath-ioPath to resolve:path-ioPath to resolve<path-ioOriginal locationpath-io New location=path-ioOriginal locationpath-ioWhere to put copy?path-ioExecutable file namepath-ioPath to found executable@path-ioSet of directories to search inpath-ioFilename of interestpath-io Absolute path to file (if found)Apath-ioSet of directories to search inpath-ioFilename of interestpath-io!Absolute paths to all found filesBpath-ioHow to test the filespath-ioSet of directories to search inpath-ioFilename of interestpath-io!Absolute paths to all found filesCpath-ioPath to the target filepath-ioPath to the link to be createdDpath-ioPath to the target directorypath-ioPath to the link to be createdEpath-ioPath to the link to be removedFpath-io Symlink pathHpath-ioDirectory to create the file inpath-ioFile name template, see Lpath-ioCallback that can use the fileIpath-ioDirectory to create the file inpath-ioDirectory name template, see Lpath-io#Callback that can use the directoryJpath-ioFile name template, see Lpath-ioCallback that can use the fileKpath-ioDirectory name template, see Lpath-io#Callback that can use the directoryLpath-ioDirectory to create file inpath-ioFile name template; if the template is "foo.ext" then the created file will be  "fooXXX.ext" where XXX is some random numberpath-ioName of created file and its tMpath-ioDirectory to create file inpath-ioFile name template, see Lpath-ioName of created file and its tNpath-ioDirectory to create file inpath-ioDirectory name template, see Lpath-io#Name of created temporary directoryWpath-ioFrom where to copypath-ioWhat to modifympath-ioOriginal actionpath-iob argumentpath-io Lifted actionopath-ioOriginal actionpath-ioFirst b argumentpath-ioSecond b argumentppath-ioOriginal actionpath-ioFirst b argumentpath-ioSecond argument !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRST UVWXYZ[ !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRST UVWXYZ[                   !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{y|}~vwyvwyypqy$path-io-1.8.2-50fveXuAsmjBnL1Jia19pSPath.IOpath-io System.IO isFullErrorSystem.Process createProcessSystem.IO.ErrorpermissionErrorTypeillegalOperationErrorTypedoesNotExistErrorTypedirectory-1.3.8.1 System.Directory.Internal.CommonXdgDirectoryList XdgDataDirs XdgConfigDirs XdgDirectoryXdgData XdgConfigXdgCacheXdgState Permissionsreadablewritable executable searchableSystem.DirectoryemptyPermissionssetOwnerReadablesetOwnerWritablesetOwnerExecutablesetOwnerSearchableAnyPathAbsPathRelPathcanonicalizePath makeAbsolute makeRelativemakeRelativeToCurrentDir WalkAction WalkFinish WalkExclude createDircreateDirIfMissing ensureDir removeDirremoveDirRecurremovePathForcibly renameDir renamePathlistDir listDirRel listDirRecurlistDirRecurRel copyDirRecur copyDirRecur'walkDir walkDirRel walkDirAccumwalkDirAccumRel getCurrentDir setCurrentDirwithCurrentDir getHomeDirgetAppUserDataDirgetUserDocsDir getTempDir getXdgDir getXdgDirList resolveFile resolveFile' resolveDir resolveDir' removeFile renameFilecopyFile getFileSizefindExecutablefindFile findFiles findFilesWithcreateFileLink createDirLink removeDirLinkgetSymlinkTarget isSymlink withTempFile withTempDirwithSystemTempFilewithSystemTempDir openTempFileopenBinaryTempFile createTempDir doesPathExist doesFileExist doesDirExistisLocationOccupiedforgivingAbsenceignoringAbsencegetPermissionssetPermissionscopyPermissions getAccessTime setAccessTimesetModificationTimegetModificationTime$fAnyPathSomeBase$fAnyPathSomeBase0 $fAnyPathPath$fAnyPathPath0$fEqWalkAction$fShowWalkAction!path-0.9.5-J24HHkIahyjIS54cYAPQ18Path.Internal.PosixPathfilepath-1.4.100.4System.FilePath.Posix normaliseghc-prim GHC.TypesTruebaseisDoesNotExistErrorcopyDirRecurGenGHC.BaseMonoidwalkDirAccumWithIO GHC.MaybeNothingFalseJustliftDGHC.IOFilePathliftD2liftD2' toFilePath' toFilePathignoringIOErrorsGHC.IO.Handle.TypesHandle