Expand description
High-performance virtual and network filesystems for macOS, Linux, and Windows.
Backends implement Filesystem (and optionally NetworkFilesystem) against one
portable data model. Platform adapters use FSKit on macOS, FUSE on Linux, and ProjFS
on Windows. Opt-in raw events expose native requests without adding allocations
to the default path.
This crate provides no filesystem implementation or storage policy. Inode
indexing, caching, synchronization, consistency, and persistence belong to
the downstream type implementing Filesystem.
Modules§
- raw
- Opt-in borrowed native requests and callback buffers.
Structs§
- Directory
Entry - Error
- A filesystem error represented by
FSK’s stable, positive error code. - Local
File - A locally materialized file managed by a network backend.
- Metadata
- Mount
- The resource supplied by macOS when mounting a network filesystem.
- Mount
Options - Mount
Session - Network
Configuration - Network-specific behavior communicated to the Swift
FSKitlayer. - Read
Directory Result - SetMetadata
- StatFs
Enums§
- File
Type - Kernel
Cache Policy - The kernel caching behavior requested by a network backend.
- Network
File - The data source selected when
FSKitopens a network file.
Constants§
- ABI_
VERSION - Version of the C ABI implemented by this crate.
- ROOT_
INODE - The root inode. Platform adapters treat inode values as opaque identifiers.
Traits§
- Directory
Sink - Filesystem
- Cross-platform filesystem operations.
- Network
Filesystem - Additional lifecycle hooks for lazy network filesystems.