h"      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ Safe-Inferred!unstableportable Safe-Inferred]  !"#$%&'()*+,-./0123456789:;<=>?@AEBDCFGHIJKLMNOPQRSTVUXWZY\[^]`_bakcdefghjinmlopqrstuwvxyz{|}~-.|}~()*+,NOP uwvqrstST{xyzJKLM;<=>?@Akcdefghjiop123456789:VUXWZY\[^]`_baIEBDC FGHnml !"#$%&'QR/0 Safe-Inferred directorySearch paths for various application data, as specified by the  http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG Base Directory Specification.!The list of paths is split using #, which on Windows is a semicolon.Note: On Windows,  and  usually yield the same result. directory+For data files (e.g. images). It uses the  XDG_DATA_DIRS? environment variable. On non-Windows systems, the default is /usr/local/share/ and  /usr/share/. On Windows, the default is  %PROGRAMDATA% or %ALLUSERSPROFILE% (e.g. C:/ProgramData). directory&For configuration files. It uses the XDG_CONFIG_DIRS? environment variable. On non-Windows systems, the default is /etc/xdg. On Windows, the default is  %PROGRAMDATA% or %ALLUSERSPROFILE% (e.g. C:/ProgramData). directorySpecial directories for storing user-specific application data, configuration, and cache files, as specified by the  http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html XDG Base Directory Specification.Note: On Windows,  and $ usually map to the same directory. directory+For data files (e.g. images). It uses the  XDG_DATA_HOME? environment variable. On non-Windows systems, the default is ~/.local/share. On Windows, the default is  %APPDATA% (e.g.  C:/Users//AppData/Roaming9). Can be considered as the user-specific equivalent of  /usr/share. directory&For configuration files. It uses the XDG_CONFIG_HOME? environment variable. On non-Windows systems, the default is  ~/.config. On Windows, the default is  %APPDATA% (e.g.  C:/Users//AppData/Roaming9). Can be considered as the user-specific equivalent of /etc. directory3For non-essential files (e.g. cache). It uses the XDG_CACHE_HOME? environment variable. On non-Windows systems, the default is ~/.cache. On Windows, the default is %LOCALAPPDATA% (e.g.  C:/Users//AppData/Local9). Can be considered as the user-specific equivalent of  /var/cache. directory8POSIX: either file or directory link; Windows: file link directoryWindows only: directory link directoryA generator with side-effects. directory Similar to ,$ but only catches a specify kind of R" as specified by the predicate. directoryAttempt to perform the given action, silencing any IO exception thrown by it. directory&Given a list of path segments, expand . and ..7. The path segments must not contain path separators. directory%Convert to the right kind of slashes. directoryRemove redundant trailing slashes and pick the right kind of slash. directoryConvert empty paths to the current directory, otherwise leave it unchanged. directory Similar to  but empty paths stay empty. directory Similar to  but:empty paths stay empty, parent dirs (..) are expanded, andpaths starting with \\?\ are preserved.9The goal is to preserve the meaning of paths better than . directoryCheck whether the given  is considered a directory by the operating system. This affects the choice of certain functions e.g.  vs  . directoryReturn whether the given  is a link. directoryTruncate the destination file and then copy the contents of the source file to the destination file. If the destination file already exists, its attributes shall remain unchanged. Otherwise, its attributes are reset to the defaults. directory&Copy all data from a file to a handle. directory7Copy data from one handle to another until end of file. directorySource filename directoryDestination filename directory Source file directoryDestination handle directory Source handle directoryDestination handle,  Safe-Inferred  Safe-Inferred= directoryOn POSIX, equivalent to . directoryConvert a path into an absolute path. If the given path is relative, the current directory is prepended and the path may or may not be simplified. If the path is already absolute, the path is returned unchanged. The function preserves the presence or absence of the trailing path separator.If the path is already absolute, the operation never fails. Otherwise, the operation may throw exceptions.1Empty paths are treated as the current directory. directoryGet the contents of the PATH environment variable. directory$HOME is preferred, because the user has control over it. However, POSIX doesn't define it as a mandatory variable, so fall back to  getpwuid_r.1unstable unportable Safe-Inferred"(c) The University of Glasgow 2001/BSD-style (see the file libraries/base/LICENSE)libraries@haskell.orgstableportable Safe-InferredJ7 directory+Get the permissions of a file or directory.On Windows, the < permission corresponds to the "read-only" attribute. The  permission is set if the file extension is of an executable file type. The  permission is always set.-On POSIX systems, this returns the result of access.The operation may fail with:"> if the user is not permitted to access the permissions, or$) if the file or directory does not exist. directory+Set the permissions of a file or directory.1On Windows, this is only capable of changing the  permission, which corresponds to the "read-only" attribute. Changing the other permissions has no effect. On POSIX systems, this sets the owner permissions.The operation may fail with:"; if the user is not permitted to set the permissions, or$) if the file or directory does not exist. directoryCopy the permissions of one file to another. This reproduces the permissions more accurately than using  followed by .5On Windows, this copies only the read-only attribute.(On POSIX systems, this is equivalent to stat followed by chmod. directory 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:" The process has insufficient privileges to perform the operation. [EROFS, EACCES]%8 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]$$ There is no path to the directory. [ENOENT, ENOTDIR]  Insufficient resources (virtual memory, process file descriptors, physical disk space, etc.) are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]InappropriateType6 The path refers to an existing non-directory object. [EEXIST] directory parents dir creates a new directory dir/ if it doesn't exist. If the first argument is  the function will also create all parent directories if they are missing. directory 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]$ The directory does not exist. [ENOENT, ENOTDIR]" The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY, ENOTEMPTY, EEXIST]UnsupportedOperation The implementation does not support removal in this situation. [EINVAL]InappropriateType9 The operand refers to an existing non-directory object.  [ENOTDIR] directory dir removes an existing directory dir together with its contents and subdirectories. Within this directory, symbolic links are removed without affecting their targets.#On Windows, the operation fails if dir is a directory symbolic link. directoryremovePathRecursive path+ removes an existing file or directory at path together with its contents and subdirectories. Symbolic links are removed without affecting their the targets. directoryremoveContentsRecursive dir( removes the contents of the directory dir recursively. Symbolic links are removed without affecting their the targets. directoryRemoves 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. directory file2 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]$ The file does not exist. [ENOENT, ENOTDIR]" The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY]InappropriateType. The operand refers to an existing directory. [EPERM, EINVAL] directory old new0 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, renameDirectory fails if the new directory already exists.The operation may fail with: HardwareFault$ A physical I/O error has occurred. [EIO]InvalidArgument/ Either operand is not a valid directory name. [ENAMETOOLONG, ELOOP]$ The original directory does not exist, or there is no path to the target. [ENOENT, ENOTDIR]" The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]  Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY, ENOTEMPTY, EEXIST]UnsupportedOperation The implementation does not support renaming in this situation. [EINVAL, EXDEV]InappropriateType9 Either path refers to an existing non-directory object. [ENOTDIR, EISDIR] directory old new9 changes the name of an existing file system object from old to new . If the new9 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]$ The original file does not exist, or there is no path to the target. [ENOENT, ENOTDIR]" The process has insufficient privileges to perform the operation. [EROFS, EACCES, EPERM]  Insufficient resources are available to perform the operation.  [EDQUOT, ENOSPC, ENOMEM, EMLINK]UnsatisfiedConstraints9 Implementation-dependent constraints are not satisfied. [EBUSY]UnsupportedOperation The implementation does not support renaming in this situation. [EXDEV]InappropriateType. Either path refers to an existing directory. ,[ENOTDIR, EISDIR, EINVAL, EEXIST, ENOTEMPTY] directoryRename 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]$ The original file does not exist, or there is no path to the target. [ENOENT, ENOTDIR]" 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] directoryCopy a file with its permissions. If the destination file already exists, it is replaced atomically. Neither path may refer to an existing directory. No exceptions are thrown if the permissions could not be copied. directoryCopy the contents of a source file to a destination file, replacing the destination file atomically via withReplacementFile, resetting the attributes of the destination file to the defaults. directoryA helper function useful for replacing files in an atomic manner. The function creates a temporary file in the directory of the destination file, opens it, performs the main action with its handle, closes it, performs the post-action with its path, and finally replaces the destination file with the temporary file. If an error occurs during any step of this process, the temporary file is removed and the destination file remains untouched. directoryCopy a file with its associated metadata. If the destination file already exists, it is overwritten. There is no guarantee of atomicity in the replacement of the destination file. Neither path may refer to an existing directory. If the source and/or destination are symbolic links, the copy is performed on the targets of the links.0On Windows, it behaves like the Win32 function  https://msdn.microsoft.com/en-us/library/windows/desktop/aa363851.aspxCopyFile, which copies various kinds of metadata including file attributes and security resource properties.On Unix-like systems, permissions, access time, and modification time are preserved. If possible, the owner and group are also preserved. Note that the very act of copying can change the access time of the source file, hence the access times of the two files may differ after the operation completes. directoryMake a path absolute, normalize the path, and remove as many indirections from it as possible. Any trailing path separators are discarded via . Additionally, on Windows the letter case of the path is canonicalized.Note: This function is a very big hammer. If you only need an absolute path,  is sufficient for removing dependence on the current working directory.1Indirections include the two special directories . and .., as well as any symbolic links (and junction points on Windows). The input path need not point to an existing file or directory. Canonicalization is performed on the longest prefix of the path that points to an existing file or directory. The remaining portion of the path that does not point to an existing file or directory will still be normalized, but case canonicalization and indirection removal are skipped as they are impossible to do on a nonexistent path.Most programs should not worry about the canonicity of a path. In particular, despite the name, the function does not truly guarantee canonicity of the returned path due to the presence of hard links, mount points, etc.If the path points to an existing file or directory, then the output path shall also point to the same file or directory, subject to the condition that the relevant parts of the file system do not change while the function is still running. In other words, the function is definitively not atomic. The results can be utterly wrong if the portions of the path change while this function is running.8Since some indirections (symbolic links on all systems, .. on non-Windows systems, and junction points on Windows) are dependent on the state of the existing filesystem, the function can only make a conservative attempt by removing such indirections from the longest prefix of the path that still points to an existing file or directory.(Note that on Windows parent directories .. are always fully expanded before the symbolic links, as consistent with the rest of the Windows API (such as GetFullPathName6). In contrast, on POSIX systems parent directories .. are expanded alongside symbolic links from left to right. To put this more concretely: if L is a symbolic link for R/P, then on Windows L\.. refers to .%, whereas on other operating systems L/.. refers to R. Similar to , passing an empty path is equivalent to passing the current directory.canonicalizePath can resolve at least 64 indirections in a single path, more than what is supported by most operating systems. Therefore, it may return the fully resolved path even though the operating system itself would have long given up.On Windows XP or earlier systems, junction expansion is not performed due to their lack of GetFinalPathNameByHandle.Changes since 1.2.3.0: The function has been altered to be more robust and has the same exception behavior as .Changes since 1.3.0.0: The function no longer preserves the trailing path separator. File symbolic links that appear in the middle of a path are properly dereferenced. Case canonicalization and symbolic link expansion are now performed on Windows. directoryConvert a path into an absolute path. If the given path is relative, the current directory is prepended and then the combined result is normalized. If the path is already absolute, the path is simply normalized. The function preserves the presence or absence of the trailing path separator unless the path refers to the root directory /.If the path is already absolute, the operation never fails. Otherwise, the operation may fail with the same exceptions as . directoryAdd or remove the trailing path separator in the second path so as to match its presence in the first path.(internal API) directoryConstruct a path relative to the current directory, similar to .3The operation may fail with the same exceptions as . directory.Given the name or path of an executable file,  searches for such a file in a list of system-defined locations, which generally includes PATH and possibly more. The full path to the executable is returned if found. For example, (findExecutable "ghc")* would normally give you the path to GHC.The path returned by  name8 corresponds to the program that would be executed by  http://hackage.haskell.org/package/process/docs/System-Process.html#v:createProcess createProcess$ when passed the same string (as a  RawCommand, not a  ShellCommand), provided that name3 is not a relative path with more than one segment. On Windows,  calls the Win32 function  6https://msdn.microsoft.com/en-us/library/aa365527.aspx SearchPath, which may search other places before checking the directories in the PATH environment variable. Where it actually searches depends on registry settings, but notably includes the directory containing the current executable.8On non-Windows platforms, the behavior is equivalent to ( using the search directories from the PATH environment variable and testing each file for executable permissions. Details can be found in the documentation of . directorySearch for executable files in a list of system-defined locations, which generally includes PATH and possibly more.On Windows, this  only returns the first ocurrence4, if any. Its behavior is therefore equivalent to .9On non-Windows platforms, the behavior is equivalent to ' using the search directories from the PATH environment variable. Details can be found in the documentation of . directoryGiven a name or path,  appends the  to the query and searches for executable files in the list of given search directories and returns all occurrences.The behavior is equivalent to  using the given search directories and testing each file for executable permissions. Details can be found in the documentation of .(Unlike other similarly named functions,  does not use  SearchPath from the Win32 API. The behavior of this function on Windows is therefore equivalent to those on non-Windows platforms. directory/Test whether a file has executable permissions. directorySearch through the given list of directories for the given file.The behavior is equivalent to , returning only the first occurrence. Details can be found in the documentation of . directorySearch through the given list of directories for the given file and returns all paths where the given file exists.The behavior is equivalent to 1. Details can be found in the documentation of . directorySearch through a given list of directories for a file that has the given name and satisfies the given predicate and return the path of the first occurrence. The directories are checked in a left-to-right order.1This is essentially a more performant version of  that always returns the first result, if any. Details can be found in the documentation of . directory!findFilesWith predicate dirs name, searches through the list of directories (dirs ) for files that have the given name and satisfy the given  predicate ands return the paths of those files. The directories are checked in a left-to-right order and the paths are returned in the same order.If the name5 is a relative path, then for every search directory dir, the function checks whether dir  name. exists and satisfies the predicate. If so, dir  name is returned as one of the results. In other words, the returned paths can be either relative or absolute depending on the search directories were used. If there are no search directories, no results are ever returned.If the name is an absolute path, then the function will return a single result if the file exists and satisfies the predicate and no results otherwise. This is irrespective of what search directories were given. directoryFilename extension for executable files (including the dot if any) (usually "" on POSIX systems and ".exe" on Windows or OS/2). directory Similar to +, but always includes the special entries (. and ..&). (This applies to Windows as well.)3The operation may fail with the same exceptions as . directory dir returns a list of all entries in dir without the special entries (. and ..).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]$% The directory does not exist. [ENOENT, ENOTDIR]" The process has insufficient privileges to perform the operation. [EACCES]  Insufficient resources are available to perform the operation. [EMFILE, ENFILE]InappropriateType< The path refers to an existing non-directory object.  [ENOTDIR] directory9Obtain 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]$8 There is no path referring to the working directory. [EPERM, ENOENT, ESTALE...]" The process has insufficient privileges to perform the operation. [EACCES]  Insufficient resources are available to perform the operation.UnsupportedOperation The operating system has no notion of current working directory. directory/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]$! The directory does not exist. [ENOENT, ENOTDIR]" 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] directoryRun an  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 . directory#Obtain the size of a file in bytes. directoryTest 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. directoryThe operation  returns  if the argument file exists and is either a directory or a symbolic link to a directory, and  otherwise. directoryThe operation  returns 9 if the argument file exists and is not a directory, and  otherwise. directory 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.6Windows-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. directory 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 .!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  and is therefore atomic.6Windows-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. directoryRemove 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. directoryCheck whether an existing path is a symbolic link. If path" is a regular file or directory,  is returned. If path does not exist or is otherwise inaccessible, an exception is thrown (see below).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.The operation may fail with:$( if the symbolic link does not exist; or"; if the user is not permitted to read the symbolic link. directoryRetrieve the target path of either a file or directory symbolic link. The returned path may not be absolute, 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. directoryObtain the time at which the file or directory was last accessed.The operation may fail with:"< if the user is not permitted to read the access time; or$) 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.07 or later and the underlying filesystem supports them. directoryObtain the time at which the file or directory was last modified.The operation may fail with:" if the user is not permitted to read the modification time; or$) 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.07 or later and the underlying filesystem supports them. directoryChange the time at which the file or directory was last accessed.The operation may fail with:"= if the user is not permitted to alter the access time; or$) 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. directoryChange the time at which the file or directory was last modified.The operation may fail with:" if the user is not permitted to alter the modification time; or$) 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. directory*Returns 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  or  instead. On Unix,  behaves as follows:Returns $HOME env variable if set (including to an empty string).*Otherwise uses home directory returned by  getpwuid_r using the UID of the current proccesses user. This basically reads the etc?passwd file. An empty home directory field is considered valid.On Windows, the system is queried for a suitable path; a typical path might be  C:/Users/.The operation may fail with:UnsupportedOperation6 The operating system has no notion of home directory.$ The home directory for the current user does not exist, or cannot be found. directoryObtain 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 , this function provides a more fine-grained hierarchy as well as greater flexibility for the user. On Windows,  and 8 usually map to the same directory unless overridden.Refer to the docs of  for more details.The second argument is usually the name of the application. Since it will be integrated into the path, it must consist of valid path characters. Note: if the second argument is an absolute path, it will just return the second argument.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).As of 1.3.5.0, the environment variable is ignored if set to a relative path, per revised XDG Base Directory Specification. See  /https://github.com/haskell/directory/issues/100#100. directory Similar to 3 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. directoryObtain the path to a special directory for storing user-specific application data (traditional Unix location). Newer applications may prefer the the XDG-conformant location provided by  ( https://github.com/haskell/directory/issues/6#issuecomment-96521020migration guide).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.$ The home directory for the current user does not exist, or cannot be found. directory.Returns 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  or  instead. On Unix,  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.$ The document directory for the current user does not exist, or cannot be found. directory2Returns the current directory for temporary files. On Unix,  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.  directoryCreate its parents too? directory*The path to the directory you want to make directoryOld path directoryNew path directorySource filename directoryDestination filename directorySource filename directoryDestination filename directory Post-action directoryDestination file directory Post-action directory Main action directory Source file directoryDestination file directoryDirectory to execute in directoryAction to be executed directorypath to the target file directorypath of the link to be created directorypath to the target directory directorypath of the link to be created directorywhich special directory directorya relative path that is appended to the path; if empty, the base path is returned directorywhich special directory list directory/a relative path that is appended to the path Safe-Inferred !"!#!$!%&'() * +,-./01020304565758595:5;5<5=5>5?5@5A5B5C5D5EFGFHFIFJFKLMLNOPQRSTSUSVSWXYXZX[X\X]X^_`_abcbdefegehijikilim,n.opqrstutvtwtxyzy{y|i}i~                                                   &&&&&            iy      directory-1.3.6.0!System.Directory.Internal.PreludeSystem.Directory.InternalSystem.Directory System.Directory.Internal.Config System.Directory.Internal.CommonSystem.FilePathsearchPathSeparatorremoveDirectory removeFile%System.Directory.Internal.C_utimensatSystem.Directory.Internal.Posix System.IO isFullError normalise!System.Directory.Internal.WindowsbaseGHC.Base<>memptymconcatGHC.PtrPtr Data.VoidVoidSystem.TimeouttimeoutSystem.Environment lookupEnvgetEnvgetArgs System.Exit exitFailure Control.Monadunless replicateM_<=<>=>Data.Traversablefor Control.ArrowsecondopenBinaryTempFilewithBinaryFile GHC.IO.HandlehCloseGHC.IO.Handle.FDstderrGHC.IO.Handle.TexthGetBufhPutBuf hPutStrLnhPutStrSystem.IO.Error catchIOError modifyIOErrorioeSetFileNameioeSetLocationioeSetErrorStringioeGetLocationioeGetErrorStringioeGetErrorTypepermissionErrorTypeillegalOperationErrorTypeisPermissionErrorisIllegalOperationisDoesNotExistErrorisAlreadyExistsError mkIOError tryIOErrorControl.Exception.Basebracket_finallybracket onExceptiontry GHC.Conc.Sync killThreadforkIOSystem.Posix.Internals withFilePathSystem.Posix.Types EpochTimeForeign.C.ErrorthrowErrnoPathIfMinus1_throwErrnoIfNullthrowErrnoIfMinus1Retry_throwErrnoIfMinus1_Foreign.C.String withCWStringpeekCWStringLen withCString peekCStringCStringCWStringForeign.Marshal.Array withArray allocaArrayForeign.Marshal.Utils maybeWithwithForeign.Marshal.AllocallocaBytesAligned allocaBytesallocaGHC.IO.ExceptionUnsupportedOperationInappropriateType OtherError IOErrorTypehFlushstdoutGHC.IO.Handle.TypesHandleGHC.IO.EncodinggetFileSystemEncoding GHC.IORef writeIORef readIORefnewIORefIORefGHC.IOmaskthrowIOcatch userErrorIOError Data.Foldablefor_ traverse_Foreign.C.TypesCUCharCUShortCIntCLongCULongCWcharCTimeForeign.Storablepokepeek pokeByteOff peekByteOff pokeElemOff peekElemOff alignmentsizeOfStorable GHC.IO.IOMode WriteModeReadModeIOModeplusPtrnullPtr GHC.UnicodetoUppertoLowerisAlphaisAscii Data.Bits complement.|..&. Data.Maybe catMaybes maybeToList fromMaybe Data.FunctiononGHC.MVarputMVarreadMVartakeMVar newEmptyMVarwhenGHC.Exception.Type SomeExceptionXdgDirectoryList XdgDataDirs XdgConfigDirs XdgDirectoryXdgData XdgConfigXdgCache Permissionsreadablewritable executable searchableFileTypeFile SymbolicLink Directory DirectoryLinkListTunListT emptyListT maybeToListT listToListT liftJoinListT listTHead listTToListandMsequenceWithIOErrors_tryIOErrorTypeignoreIOExceptionsspecializeErrorStringioeAddLocation expandDotsnormalisePathSepsnormaliseTrailingSep emptyToCurDir simplifyPosixsimplifyWindowsfileTypeIsDirectoryfileTypeIsLinkcopyFileContentscopyFileToHandlecopyHandleDataModeMetadata c_realpathc_freecreateDirectoryInternalremovePathInternalrenamePathInternalsimplify c_PATH_MAX withRealpathcanonicalizePathWithcanonicalizePathSimplifyfindExecutablesLazyInternalexeExtensionInternalgetDirectoryContentsInternalgetCurrentDirectoryInternalprependCurrentDirectorysetCurrentDirectoryInternallinkToDirectoryIsDirectorycreateSymbolicLinkreadSymbolicLinkgetSymbolicLinkMetadatagetFileMetadatafileTypeFromMetadatafileSizeFromMetadataaccessTimeFromMetadatamodificationTimeFromMetadataposix_accessTimeHiResposix_modificationTimeHiResmodeFromMetadata allWriteMode hasWriteMode setWriteMode setFileModesetFilePermissionsgetAccessPermissionssetAccessPermissionscopyOwnerFromStatuscopyGroupFromStatustryCopyOwnerAndGroupFromStatuscopyFileWithMetadataInternalsetTimesgetPathgetHomeDirectoryInternalgetXdgDirectoryFallbackgetXdgDirectoryListFallbackgetAppUserDataDirectoryInternal!getUserDocumentsDirectoryInternalgetTemporaryDirectoryInternalemptyPermissionssetOwnerReadablesetOwnerWritablesetOwnerExecutablesetOwnerSearchablegetPermissionssetPermissionscopyPermissionscreateDirectorycreateDirectoryIfMissingremoveDirectoryRecursiveremovePathForciblyrenameDirectory renameFile renamePathcopyFilecopyFileWithMetadatacanonicalizePath makeAbsolutemakeRelativeToCurrentDirectoryfindExecutablefindExecutablesfindExecutablesInDirectoriesfindFile findFiles findFileWith findFilesWith exeExtensiongetDirectoryContents listDirectorygetCurrentDirectorysetCurrentDirectorywithCurrentDirectory getFileSize doesPathExistdoesDirectoryExist doesFileExistcreateFileLinkcreateDirectoryLinkremoveDirectoryLinkpathIsSymbolicLinkisSymbolicLinkgetSymbolicLinkTarget getAccessTimegetModificationTime setAccessTimesetModificationTimegetHomeDirectorygetXdgDirectorygetXdgDirectoryListgetAppUserDataDirectorygetUserDocumentsDirectorygetTemporaryDirectory++ghc-primGHC.PrimseqGHC.Listfilterzipprint Data.Tuplefstsnd otherwisemap$GHC.Real fromIntegral realToFracGHC.EnumBoundedminBoundmaxBoundEnumpredsuccenumFromThenTo enumFromTo enumFromThenenumFromfromEnumtoEnum GHC.ClassesEq==/= GHC.FloatFloatingatanhacoshasinhtanhcoshsinhatanacosasintancossinlogBase**sqrtlogpiexp Fractionalrecip fromRational/IntegraldivModquotRemmoddivrem toIntegerquotMonad>>>>=returnFunctorfmap<$GHC.NumNumsignumabs*+negate fromInteger-Ord<<=>maxmincompare>=GHC.ReadRead readsPrecreadListReal toRational RealFloatatan2isIEEEisNegativeZeroisDenormalized isInfiniteisNaN scaleFloat significandexponent encodeFloat decodeFloat floatRange floatRadix floatDigitsRealFracfloorceilingroundproperFractiontruncateGHC.ShowShowshowListshow showsPrecControl.Monad.Fail MonadFailfail Applicative<**><*>pureFoldableelemminimummaximumfoldr1productsumfoldl1nullfoldrfoldllengthfoldMap Traversablesequence sequenceAtraversemapM SemigroupMonoidmappend GHC.TypesBoolFalseTrueCharDoubleFloatIntinteger-wired-inGHC.Integer.TypeInteger GHC.MaybeMaybeJustNothingOrderingGTLTEQRationalIOWord Data.EitherEitherRightLeftreadIOreadLn appendFile writeFilereadFileinteract getContentsgetLinegetCharputStrLnputStrputCharioErrorFilePathnotElemallanyorand concatMapconcat sequence_mapM_ Data.OldListunwordswordsunlineslines Text.Readreadreadseitherlex readParenText.ParserCombinators.ReadPReadSlcmgcd^^^oddeven showParen showStringshowCharshowsShowSunzip3unzipzipWith3zipWithzip3!!lookupreversebreakspansplitAtdroptake dropWhile takeWhilecycle replicaterepeatiteratescanr1scanrscanl1scanlinitlasttailheadmaybe Data.Functor<$>uncurrycurrysubtractasTypeOfuntil$!flip.constid=<<StringGHC.Err undefinederrorWithoutStackTraceerror&&||notfilepath-1.4.2.1System.FilePath.Posix CTimeSpec c_utimensat c_AT_FDCWD utimeOmit toCTimeSpecremovePathRecursiveremoveContentsRecursiveatomicCopyFileContentswithReplacementFiledropTrailingPathSeparatormatchTrailingSeparator makeRelative isExecutable