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
45
46
47
48
49
50
51
52
53
//! A capability-based API modeled after [`async_std`].
//!
//! This corresponds to [`async_std`].
//!
//! Capability-based APIs represent access to external resources as values
//! which can be passed around between different parts of a program.
//!
//! Two notable features are the [`Dir`] and [`Pool`] types:
//! - `Dir` represents an open directory in a filesystem. Instead of opening
//! files by absolute paths or paths relative to the current working
//! directory, files are opened via paths relative to a `Dir`. The concepts
//! of a process-wide "current working directory" and a single global
//! filesystem namespace are de-emphasized.
//! - `Pool` represents a set of network addresses. Instead of allowing
//! applications to request access to any address and then applying
//! process-wide filtering rules, filtering rules are built into pools which
//! may be passed through the program.
//!
//! On WASI, use of this library closely reflects the underlying system
//! API, so it avoids compatibility layers.
//!
//! [`Dir`]: fs::Dir
//! [`Pool`]: net::Pool
// async_std doesn't have "can_vector".
// async_std doesn't have "write_all_vectored".
// Disable `net` on WASI until it has networking support.
pub use ambient_authority_known_at_compile_time;
pub use ;
// Re-export `async_std` to make it easy for users to depend on the same
// version we do, because we use its types in our public API.
pub use async_std;
// And these are also part of our public API
pub use ipnet;
pub use io_lifetimes;