Documentation

UVSlotUnsafe wrap a slot which may not have a MVar in blocking table, i.e. the blocking table need to be resized.

Peek loop data pointer from uv loop pointer.

uv_run with usafe FFI.

uv_run with safe FFI.

Just pass null pointer as SocketAddr to disconnect

Terminal mode.

When in TTY_MODE_RAW mode, input is always available character-by-character, not including modifiers. Additionally, all special processing of characters by the terminal is disabled, including echoing input characters. Note that CTRL+C will no longer cause a SIGINT when in this mode.

00700 user (file owner) has read, write and execute permission

00400 user has read permission

00200 user has write permission

00100 user has execute permission

00070 group has read, write and execute permission

00040 group has read permission

00020 group has write permission

00010 group has execute permission

00007 others have read, write and execute permission

00004 others have read permission

00002 others have write permission

00001 others have execute permission

Default mode for file open, 0x666(readable and writable).

Default mode for open, 0x755.

This is the file type mask.

This is the file type constant of a symbolic link.

This is the file type constant of a directory file.

This is the file type constant of a regular file.

The file is opened in append mode. Before each write, the file offset is positioned at the end of the file.

The file is created if it does not already exist.

File IO is done directly to and from user-space buffers, which must be aligned. Buffer size and address should be a multiple of the physical sector size of the block device, (DO NOT USE WITH Z-IO's BufferedIO)

If the path is not a directory, fail the open. (Not useful on regular file)

Note O_DIRECTORY is not supported on Windows.

The file is opened for synchronous IO. Write operations will complete once all data and a minimum of metadata are flushed to disk.

Note O_DSYNC is supported on Windows via FILE_FLAG_WRITE_THROUGH.

If the O_CREAT flag is set and the file already exists, fail the open.

Note In general, the behavior of O_EXCL is undefined if it is used without O_CREAT. There is one exception: on Linux 2.6 and later, O_EXCL can be used without O_CREAT if pathname refers to a block device. If the block device is in use by the system (e.g., mounted), the open will fail with the error EBUSY.

Atomically obtain an exclusive lock.

Note UV_FS_O_EXLOCK is only supported on macOS and Windows. (libuv: Changed in version 1.17.0: support is added for Windows.)

Do not update the file access time when the file is read.

Note O_NOATIME is not supported on Windows.

If the path identifies a terminal device, opening the path will not cause that terminal to become the controlling terminal for the process (if the process does not already have one). (Not sure if this flag is useful)

Note O_NOCTTY is not supported on Windows.

If the path is a symbolic link, fail the open.

Note O_NOFOLLOW is not supported on Windows.

Open the file in nonblocking mode if possible. (Definitely not useful in Z-IO)

Note O_NONBLOCK is not supported on Windows. (Not useful on regular file anyway)

Access is intended to be random. The system can use this as a hint to optimize file caching.

Note O_RANDOM is only supported on Windows via FILE_FLAG_RANDOM_ACCESS.

Open the file for read-only access.

Open the file for read-write access.

Access is intended to be sequential from beginning to end. The system can use this as a hint to optimize file caching.

Note O_SEQUENTIAL is only supported on Windows via FILE_FLAG_SEQUENTIAL_SCAN.

The file is temporary and should not be flushed to disk if possible.

Note O_SHORT_LIVED is only supported on Windows via FILE_ATTRIBUTE_TEMPORARY.

Open the symbolic link itself rather than the resource it points to.

The file is opened for synchronous IO. Write operations will complete once all data and all metadata are flushed to disk.

Note O_SYNC is supported on Windows via FILE_FLAG_WRITE_THROUGH.

The file is temporary and should not be flushed to disk if possible.

Note O_TEMPORARY is only supported on Windows via FILE_ATTRIBUTE_TEMPORARY.

If the file exists and is a regular file, and the file is opened successfully for write access, its length shall be truncated to zero.

Open the file for write-only access.

Beginning of the file.

Current position of the file pointer.

End of file.

Flags control copying.

• COPYFILE_EXCL: If present, uv_fs_copyfile() will fail with UV_EEXIST if the destination path already exists. The default behavior is to overwrite the destination if it exists.
• COPYFILE_FICLONE: If present, uv_fs_copyfile() will attempt to create a copy-on-write reflink. If the underlying platform does not support copy-on-write, then a fallback copy mechanism is used.
• COPYFILE_FICLONE_FORCE: If present, uv_fs_copyfile() will attempt to create a copy-on-write reflink. If the underlying platform does not support copy-on-write, or an error occurs while attempting to use copy-on-write, then an error is returned.

On Windows the flags parameter can be specified to control how the symlink will be created:

• SYMLINK_DIR: indicates that path points to a directory.
• SYMLINK_JUNCTION: request that the symlink is created using junction points.

Set the child process' user id.

This is not supported on Windows, uv_spawn() will fail and set the error to UV_ENOTSUP.

Set the child process' user id.

This is not supported on Windows, uv_spawn() will fail and set the error to UV_ENOTSUP.

Do not wrap any arguments in quotes, or perform any other escaping, when converting the argument list into a command line string.

This option is only meaningful on Windows systems. On Unix it is silently ignored.

Spawn the child process in a detached state

This will make it a process group leader, and will effectively enable the child to keep running after the parent exits.

Hide the subprocess window that would normally be created.

This option is only meaningful on Windows systems. On Unix it is silently ignored.

Hide the subprocess console window that would normally be created.

This option is only meaningful on Windows systems. On Unix it is silently ignored.

Hide the subprocess GUI window that would normally be created.

This option is only meaningful on Windows systems. On Unix it is silently ignored.