From 3bf93bc192bf362b58b2161ac05da0bb8323bf43 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 9 Nov 2026 17:33:24 +0000 Subject: docs: what is postponed or rejected stays in its own two files Docs and comments outside future-work.md and review-rejections.md say what the code does, and point nowhere else for what it doesn't: the architecture page's map, the transports' forwarders, keys with `/`, a strict swarm's registry, trust.md's "Not yet" (now saying what isn't protected, in a sentence), the topology bench, and the comments of the change benchmarks, capabilities' grantor, tokens, dissemination, refusals and topology. --- src/swarm/topology/mod.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'src/swarm/topology/mod.rs') diff --git a/src/swarm/topology/mod.rs b/src/swarm/topology/mod.rs index 2d812e5..8fae0ed 100644 --- a/src/swarm/topology/mod.rs +++ b/src/swarm/topology/mod.rs @@ -41,8 +41,7 @@ use graph::*; pub(crate) use graph::{RingAndPairs, pair_key, pair_score}; /// How members' neighbours are chosen: the graph above (`RingAndPairs`) is one way; -/// others can be tried against it in the benchmark (`docs/future-work.md`, Swappable -/// topology and dissemination). One per swarm: a node's neighbours must count it as +/// others can be tried against it in the benchmark. One per swarm: a node's neighbours must count it as /// theirs. /// /// A topology either computes a graph every node shares (`graph`: the same inputs give -- cgit v1.3.1