powersemmi / ruststream / 33865286358

97%

Build Type

push

github

Committed by web-flow

Commit Message

Land the whole 0.7 surface on one branch (#292)

* Carry the manual path's hand-written spellings in the prelude

A service without the macros feature spells by hand what the derives write, and those
impls name types the prelude did not carry: the Input spelling over SoloDeserialized for a
Deserialized type, MessageWire over SerializedWire and SerializedReply for a Serialized one,
the OutgoingDestination forms and MessageHeaders contracts of an outgoing declaration, the
PublishedThrough / OutMessages slot dictionary with the OutgoingMessageMetadata it reports,
and the FromContext binding behind an extractor parameter. Each was one more explicit import,
so the manual path could not be written from the one glob a service is told to import.

The prelude takes them from where they live: the traits and wire markers from runtime, the
declaration vocabulary from the crate root, which gains no re-export. A derive sharing its
trait's name keeps coming in under the macros feature only, so the trait namespace is imported
exactly once. The rustdoc examples that show the hand-written form import from the prelude,
and the cursor rules describe the same surface.

* Pin the macro-free lane path through the prelude

With macros off and no codec feature, the test spells both lanes exactly as the traits' rustdoc
does, imports nothing from the crate but the glob and the in-memory broker, and mounts them as
a service: a Deserialized input relayed as a Serialized reply, with the bytes asserted on both
ends. The reduced-feature CI leg runs it, since that build is the one where a lane spelling
missing from the prelude has nowhere else to come from.

* Import the manual tests and examples from the prelude alone

The explicit runtime and crate-root imports these files carried for the hand-written impls are
covered by the glob now; what stays explicit is what the prelude deliberately leaves out (the
publish pipeline's machinery, a broker capability, a policy error type).

* Add... (continued)

Coverage Stats

1126 of 1166 new or added lines in 40 files covered. (96.57%)

11 existing lines in 4 files now uncovered.

11975 of 12292 relevant lines covered (97.42%)

182.47 hits per line