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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
//! Internal facade consumed by the code generated by `ice-rpc-macros`.
//!
//! Groups the runtime internals the `#[service]` macro depends on, so the
//! stable public API of `ice-rpc` stays small. `#[doc(hidden)]`, and **not**
//! part of the public API: its symbols are semver-exempt for the consumers of
//! `ice-rpc`, but **not** for `ice-rpc-macros`.
// ── Shutdown ────────────────────────────────────────────────────────
pub use crate;
// ── Rx vocabulary, wire header and name limits ──────────────────────
pub use crate;
// The hashers the transport's own maps use, re-exported so `benches/hash_map.rs`
// can price the **shipped** implementation instead of a copy of it.
pub use crate;
// Canonical terminals behind the inherent `Observable` methods.
pub use crate;
// ── Service traits implemented by the generated code ────────────────
// `ServiceInit` stays public: it is the only one a developer implements.
pub use crate;
// ── The JSON contract, both sides ────────────────────────────────────
// One view per service: the macro implements the caller side and calls the host
// side, which registers itself once with `set_json_dispatcher`. Gated behind
// `json` alongside the module itself.
pub use crate;
// ── Diagnostics ─────────────────────────────────────────────────────
// The gateway's `version()` reports this instead of a hand-written literal.
pub use crateVERSION;
// ── Lifecycle ───────────────────────────────────────────────────────
// Escape hatch for contexts the macros cannot cover (N-API gateway, tests).
pub use crate::;
// ── Plumbing invoked by the generated entry points ──────────────────
pub use crate::;
pub use cratestart_http_server;
// ── Publish/subscribe transport ─────────────────────────────────────
// Entry points used by the generated client/server.
pub use crate;
// ── Dependency re-exports used by the generated code ────────────────
// No `futures` here: the codegen never named it, and the oneshot channel it
// used to provide now lives in `ice-rpc-rx::rt::oneshot`.
pub use async_channel;
pub use async_lock;
// Re-exported so the generated `impl` blocks (and the injection on the annotated
// trait) can name `ice_rpc::codegen::async_trait::async_trait`: the attribute macro
// expands to `::core::…` only, so reaching it through this path needs no
// `async-trait` dependency in the service crate.
pub use async_trait;
// The JSON converters are the only generated code that names `base64`. The
// request builder is emitted under `json` alone, but the invoker both JSON
// bridges dispatch to is emitted under `json` **or** `http` — the gateway needs
// it, base64 included, for a service with a `Vec<u8>` argument. Both features
// enable the dependency, so this re-export follows their union, not `json`.
pub use base64;
pub use futures_lite;
// The link-time registration surface the generated decoders use. The whole crate
// is re-exported, not just its attribute: the expansion names `linkme` itself
// (`#[linkme(crate = …)]`, the private type-check module), so the generated code
// must be able to reach it without the service crate depending on it. Gated by
// the same feature that emits the decoders.
pub use iceoryx2;
pub use linkme;
pub use log;
pub use rkyv;
pub use serde_json;