windows-overlapped-io-sys 0.1.0

Owned overlapped I/O endpoints and pinned operations for Windows IOCP and thread-pool completion.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

// Copyright (c) 2026 Mike Grier
//! Owned overlapped I/O endpoints and pinned operations for Windows.
//!
//! This crate provides the ownership, association, completion, cancellation, and
//! rundown model for overlapped I/O on top of `windows-sys`. It is the reusable
//! foundation beneath `windows-threadpool-sys`: raw I/O completion ports and the
//! object-based thread pool share endpoint and operation storage while remaining
//! distinct completion backends.
//!
//! The crate is currently in its initial development stage. No safe API has been
//! stabilized yet, because the generic overlapped-submission safety boundary is
//! still under investigation.

#![warn(missing_docs)]

#[cfg(windows)]
mod blocking;

#[cfg(windows)]
mod config;

#[cfg(windows)]
mod endpoint;

#[cfg(windows)]
mod iocp;

#[cfg(windows)]
mod operation;

#[cfg(windows)]
pub use blocking::BlockingEndpoint;

#[cfg(windows)]
pub use config::{SourceTrackingAlreadySet, set_source_tracking, source_tracking_enabled};

#[cfg(windows)]
pub use endpoint::UnassociatedEndpoint;

#[cfg(windows)]
pub use iocp::{AssociatedEndpoint, Completion, CompletionPort, OperationId, Submitted};

#[cfg(windows)]
pub use operation::{Operation, OperationState, reclaim_overlapped};