Static effect for writing paths.

Since: 0.1

Lifted createDirectory.

Since: 0.1

Lifted createDirectoryIfMissing.

Since: 0.1

Lifted removeDirectory.

Since: 0.1

Lifted removeDirectoryRecursive.

Since: 0.1

Lifted removePathForcibly.

Since: 0.1

Lifted renameDirectory.

Since: 0.1

Lifted setCurrentDirectory.

Since: 0.1

Lifted withCurrentDirectory.

Since: 0.1

Lifted removeFile.

Since: 0.1

Lifted renameFile.

Since: 0.1

Lifted renamePath.

Since: 0.1

Lifted copyFile.

Since: 0.1

Lifted copyFileWithMetadata.

Since: 0.1

Lifted createFileLink.

Since: 0.1

Lifted createDirectoryLink.

Since: 0.1

Lifted removeDirectoryLink.

Since: 0.1

Lifted setPermissions.

Since: 0.1

Lifted copyPermissions.

Since: 0.1

Lifted setAccessTime.

Since: 0.1

Lifted setModificationTime.

Since: 0.1

Runs an PathWriter effect in IO.

Since: 0.1

Directory copying config.

Since: 0.1

Determines file/directory overwrite behavior.

Since: 0.1

Determines how to name the target.

Since: 0.1

Default config for copying directories.

>>> defaultCopyDirConfig
MkCopyDirConfig {overwrite = OverwriteNone, destName = TargetNameSrc}

Since: 0.1

copyDirectoryRecursiveConfig with defaultCopyDirConfig.

Since: 0.1

copyDirectoryRecursiveConfig cfg src dest copies the src and its contents into dest e.g.

copyDirectoryRecursiveConfig cfg "path/to/foo" "path/to/bar"

will create path/to/bar/foo, path/to/bar/<target>, or copy foo's contents directly into bar, depending on the value of targetName.

The atomicity semantics are as follows:

• OverwriteNone: If an error is encountered, we roll back the successful writes by deleting the entire dest/<target>.
• OverwriteDirectories: If an error is encountered, we attempt to delete all successfully written paths/directories. Because these deletes are performed sequentially, we cannot guarantee all are removed before the process is interrupted.
• OverwriteAll: Same as OverwriteDirectories, except paths that were overwritten are not restored. That is, if a path dest/<src>/p is overwritten and an error later encountered, p is not restored.

Throws:

• PathNotFoundException: if dest does not exist.

• PathFoundException:

  • OverwriteNone and dest/<src> exists.
  • OverwriteDirectories and some dest/<target>/p would be overwritten.

Since: 0.1

Copies the symbolic link without traversing the link i.e. copy the link itself. Does not throw an exception if the target does exist. Throws an IOException if the path is not a symbolic link.

Windows: We have to distinguish between file and directory links (Posix makes no such distinction). If the target does not exist or is not considered a directory (e.g. it could also be a link), we fall back to creating a file link.

Since: 0.1

Since: 0.1

Since: 0.1

Since: 0.1

Since: 0.1

Since: 0.1

Since: 0.1

Calls removeFile if doesFileExist is True. Returns true iff the path is deleted.

Since: 0.1

Variant of removeFileIfExists that ignores the return value.

Since: 0.1

Calls removeDirectory if doesDirectoryExist is True. Returns true iff the path is deleted.

Since: 0.1

Variant of removeDirectoryIfExists that ignores the return value.

Since: 0.1

Calls removeDirectoryRecursive if doesDirectoryExist is True. Returns true iff the path is deleted.

Since: 0.1

Variant of removeDirectoryRecursiveIfExists that ignores the return value.

Since: 0.1

Calls removePathForcibly if doesPathExist is True. Returns true iff the path is deleted.

Since: 0.1

Variant of removePathForciblyIfExists that ignores the return value.

Since: 0.1

Removes a symbolic link. On Windows, attempts to distinguish file and directory links (Posix makes no distinction).

Since: 0.1

Calls removeSymbolicLink if doesSymbolicLinkExist is True. Returns true iff the path is deleted.

Since: 0.1

Variant of removeSymbolicLinkIfExists that ignores the return value.

Since: 0.1

Type representing filenames/pathnames.

This type doesn't add any guarantees over OsString.

Exceptions that occur in the IO monad. An IOException records a more specific error type, a descriptive string and maybe the handle that was used when the error was flagged.

This is the simplest representation of UTC. It consists of the day number, and a time offset from midnight. Note that if a day has a leap second added to it, it will have 86401 seconds.