JSON benchmark diagrams

JSON benchmark

Start with how the application begins, then follow data between its folders. Open an operation to see its decisions, calls, failures and cleanup. Its explanation supplies the exact contract and linked dependencies.

This view includes 2 application source files. Package and interface boundaries show checked contracts; their runtime implementations are not expanded. The views describe the checked program, not desired requirements or a recorded execution.

Where execution begins

Startup

It sets checksum and index separately, each to 0. While index is less than 5000, it sets document to parse with input "{\"id\":7,\"message\":\"hello\",\"values\":[1,2,3]}". It sets payload to document.decode for Payload. It sets encoded to stringify on a Json with value from payload. source

It sets checksum to (checksum plus payload.id) plus the byte length of encoded. It increases index by 1. After the loop, it prints checksum. If this work raises JsonError, it calls exit with status 1. source

Data flow

No calls cross the source files in this view. Follow local operations in the file sequences below.

Package boundaries

100%

Mermaid source

flowchart LR
    n0["Startup"]
    n1["json"]
    n0 -->|"parse(input) → Json"| n1

Follow the data

Each row opens the complete operations and call sites behind one pair of logical units. A grouped arrow records calls between those units; connected arrows need not belong to the same execution path.

From	To	Operations	Read
Startup	json	1	Inputs, results and call sites

Data crossing these boundaries (1 contracts)

Startup → json

1 operation, 1 site

parse

Inputs: input: string. Result: Json.

Caller or entry	Evidence
Startup	Call site · Caller explanation

Open a module

Module	Read
data.aug	Flow and sequences · Explanation
main.aug	Flow and sequences · Explanation

These are static call boundaries, not a request trace. Interface implementations and foreign internals stop at their checked contracts. Dotted arrows defer a callback or browser action. Imports alone do not imply a call.