Reading diagrams / Topic 14 of 42
IO through other packages
The rule
The direct IO topic was about a package’s own code. Running that code can still do IO somewhere else: in a package it builds on, or in a function handed to it as a value.
Yichus follows each step that code runs, into the packages it builds on and into the functions its callers hand it. Press a box, and the panel names the tables that code running there reads and writes, then says every step that could touch a table is traced. A box counts only its own code: RoleDispatch’s says “direct IO · reads 2, writes 2”, but its panel lists twelve tables that code running in it reads, jobs among them.
A box that says only “no direct IO” runs nothing that touches a table. RoleRequest builds on RolePolicy, which reads one, but none of the code RoleRequest runs reaches that read. Where code in such a package does reach a table, the box adds runs and how many tables it reads and writes. Where Yichus could not follow a step, the box adds ? not traced and the panel names the step: then a table the panel does not list is not ruled out. Nor is it where the panel says a step reads, or writes, a table the checks cannot name, as JudgmentCompletion’s does for reads: that table may be any table.
- Direct IO, or a table the panel lists for code running there: confirms that running the package’s code touches it.
- Only “no direct IO” on the box, or a table the panel does not list where every step that could touch a table is traced: rules it out.
- A ? on the box, or a step that reads or writes a table the checks cannot name: for a table the panel does not list that way, the diagram can’t tell.
Icetakes again. Press RoleDispatch, then RoleRequest.
Loading the layer diagram.
The Koa program, which has no effect sites.
Loading the layer diagram.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.