Expand description
docattest for Rust projects: the Rust adapter, which the docattest core starts and
talks to over the adapter protocol (protocol/PROTOCOL.md), and what the docattest
command of this package needs to hand over to the core.
A session (session) answers what can be read from syntax from syntax (analysis,
and the questions about text in language); what has to be compiled or run is
given to cargo (running, toolchain), in a crate the adapter generates beside the
project and never inside it.
Modules§
- language
- What needs no project: the greeting, and the questions about Rust text (blocks, doc comments, code spans, fact expressions).
- launcher
- What the
docattestcommand of this package hands over to the core (PROTOCOL.md, section 1, “Launchers”): how to start the Rust adapter, and what command runs docattest here. - protocol
- Version 1 of the docattest adapter protocol as this adapter speaks it: the data types
of the schemas in
protocol/schema/(types) and the loop that reads requests and writes responses (server). - session
- The one project
opencreates, as the protocol sees it: whatopensays, and which of the session’s methods is answered from syntax (analysis) and which by building and running programs (running).
Macros§
- observe
- A value as an [
Observation].