The context of one TopicManager::identify_admissible_outputs call: the
reference’s fifth argument, under its name (context?: TopicAdmittanceContext, ts-stack
packages/overlays/overlay/src/TopicManager.ts at f999e0c1a).
#[non_exhaustive]: build it from TopicAdmittanceContext::default() (a
real admission) or TopicAdmittanceContext::DRY_RUN, so a later field is
not a breaking change for a manager.
Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.
true: the engine is only ASKING what the manager would admit (the
GASP walk over a peer’s node, the anchor replay of a peer’s graph) and
nothing is admitted on this call. The manager must leave NO durable
trace: no storage write, no head advance, no counter an operator reads
as an admission. The reference’s dryRun.
false (the default): a submit. What the manager admits here the
engine goes on to store.