Skip to content

routes.aug diagrams ​

HTTP benchmark

Project overview · Compiled explanation

Sequences ​

Call arrows identify checked targets; loop and branch frames determine when they run. Open that target’s module to follow its implementation. Branches describe alternatives; loops describe repeated work. Native calls and interface dispatch stop at their declared contracts. Exit notes end that path; enclosing recovery and cleanup remain visible.

Reply constructor ​

It takes id as an integer, kept read-only and message as a string, kept read-only.

Receive fields: id, message. Explanation.

reply ​

reply handles GET /bench.

100%
Mermaid source
sequenceDiagram
    participant p0 as reply

    Note over p0: GET /bench
    p0->>p0: Reply(id=7, message=”hello”) · construct value
    p0-->>p0: Reply result: Reply
    Note over p0: Return Reply(id=7, message=”hello”); required cleanup<br/>runs before exit
    Note over p0: HTTP result follows declared response and error mapping;<br/>unhandled request failure returns 500

Called contracts ​

Last updated:

The world runs on language