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
54
55
56
57
58
59
60
61
62
63
64
65
//! Network-address connections.
//!
//! Submodules group the connections by source domain so the file
//! layout mirrors `time/`:
//!
//! - [`ip`] — `std::net::{Ipv4Addr, Ipv6Addr, IpAddr}` connections:
//! [`U032IPV4`] and [`U128IPV6`] (total bijections), [`IPV6IPV4`]
//! (the v4-mapped bridge as a full triple), and [`IPVXIPV4`] /
//! [`IPVXIPV6`] (one-sided sum projections extracting the V4 / V6
//! variant from `IpAddr`).
//! - [`socket`] — `std::net::{SocketAddr, SocketAddrV4, SocketAddrV6}`
//! connections: [`SOVXSOV4`] and [`SOVXSOV6`], the one-sided sum
//! projections extracting V4 / V6 from `SocketAddr`.
//!
//! Every public `Conn` constant is re-exported from this module's
//! root, so callers continue to write `connections::addr::U032IPV4`
//! (the family-flat path) without having to know which sub-module
//! hosts the implementation.
//!
//! # Naming convention
//!
//! Constants in this module use the **8-character** name shape: each
//! half is one of `A123` / `AB12` / `ABC1` / `ABCD`. The 4L+0D
//! domain-mnemonic prefixes used here:
//!
//! | code | meaning |
//! |------|--------------------------------------------------------|
//! | `IPV4` | `std::net::Ipv4Addr` |
//! | `IPV6` | `std::net::Ipv6Addr` |
//! | `IPVX` | `std::net::IpAddr` (sum of `Ipv4Addr` and `Ipv6Addr`) |
//! | `SOV4` | `std::net::SocketAddrV4` |
//! | `SOV6` | `std::net::SocketAddrV6` |
//! | `SOVX` | `std::net::SocketAddr` (sum of `SocketAddrV4` / `V6`) |
//!
//! Domain-specific types sit on the **right** of these Conns: an
//! `Ipv4Addr` is use-wise more specific than the bare `u32` it
//! shares its bit-width with, and the variant types `Ipv4Addr` /
//! `Ipv6Addr` are more specific than the sum `IpAddr` they belong
//! to. The natural composition flows `<some numeric chain> → u32 →
//! Ipv4Addr` (left-to-right) and `IpAddr → Extended<Ipv4Addr>`
//! (sum-to-variant projection).
//!
//! # One-sided vs full-triple shapes
//!
//! - **Full triples** ([`U032IPV4`], [`U128IPV6`], [`IPV6IPV4`])
//! satisfy both Galois laws plus `floor_le_ceil`. The total
//! bijections trivially; `IPV6IPV4` because `inner` is
//! order-reflecting (the v4-mapped block is a strict subset of
//! `Ipv6Addr`, giving the same "subsec room" pattern that lets
//! `TDURSECS` survive at `Duration::MIN`).
//! - **One-sided** ([`IPVXIPV4`] / [`SOVXSOV4`] via [`Conn::new_l`];
//! [`IPVXIPV6`] / [`SOVXSOV6`] via [`Conn::new_r`]) — the sum
//! types' MIN/MAX coincide with `inner`'s synthetic-end values, so
//! the full triple isn't lawful (`floor_le_ceil` would fail at the
//! source extremes). Shipped one-sided as `ConnL` / `ConnR`; only
//! the constructor's side of Galois is asserted.
//!
//! [`Conn::new_l`]: crate::conn::Conn::new_l
//! [`Conn::new_r`]: crate::conn::Conn::new_r
pub use ;
pub use ;