The state object for the I/O manager. This structure is available for both the threaded and the non-threaded RTS.

Interrupts an IO manager Wait. This will force the IO manager to process any outstanding events and timers. Also called when console events such as ctrl+c are used to break abort an I/O request.

Wake up a single thread from the I/O Manager's worker queue. This will unblock a thread blocked in processCompletion and allows the I/O manager to react accordingly to changes in timers or to process console signals. No-op if the io-manager is already running.

Entry point for the non-threaded I/O manager to be able to process completed completions. It is mostly a wrapper around processCompletion and invoked by the C thread via the scheduler.

Associate a HANDLE with the I/O manager's completion port. This must be done before using the handle with withOverlapped.

Associate a HANDLE with the current I/O manager's completion port. This must be done before using the handle with withOverlapped.

Start an overlapped I/O operation, and wait for its completion. If withOverlapped is interrupted by an asynchronous exception, the operation will be canceled using CancelIoEx.

withOverlapped waits for a completion to arrive before returning or throwing an exception. This means you can use functions like alloca to allocate buffers for the operation.

Callback that starts the overlapped I/O operation. It must return successfully if and only if an I/O completion has been queued. Otherwise, it must throw an exception, which withOverlapped will rethrow.

Specialized callback type for I/O Completion Ports calls using withOverlapped.

CallBack result type to disambiguate between the different states an I/O Completion call could be in.

Called when the completion is delivered.

Identifies an I/O operation. Used as the LPOVERLAPPED parameter for overlapped I/O functions (e.g. ReadFile, WSASend).

Warning: since the TimeoutCallback is called from the I/O manager, it must not throw an exception or block for a long period of time. In particular, be wary of throwTo and killThread: if the target thread is making a foreign call, these functions will block until the call completes.

A timeout registration cookie.

Register an action to be performed in the given number of seconds. The returned TimeoutKey can be used to later un-register or update the timeout. The timeout is automatically unregistered when it fires.

The TimeoutCallback will not be called more than once.

Be careful not to exceed maxBound :: Int, which on 32-bit machines is only 2147483647 μs, less than 36 minutes.

Update an active timeout to fire in the given number of seconds (from the time updateTimeout is called), instead of when it was going to fire. This has no effect if the timeout has already fired.

Be careful not to exceed maxBound :: Int, which on 32-bit machines is only 2147483647 μs, less than 36 minutes.

Unregister an active timeout. This is a harmless no-op if the timeout is already unregistered or has already fired.

Warning: the timeout callback may fire even after unregisterTimeout completes.

Process an IOResult and throw an exception back to the user if the action has failed, or return the result.

Signal that the I/O action was successful.

Signal that the I/O action has failed with the given reason.

Signal that the I/O action has failed with the given reason. Polymorphic in successful result type.

Get the last system error produced in the current thread.

A file handle registration cookie.