on master help sign in
gall-guide: scry - rephrase ~ / [~ ~] scry result explanation
3a6a4e1Tinnus Napbus
content/docs/userspace/gall-guide/10-scry.md+4−4
@@ -106,10 +106,10 @@ example, a scry of `.^(update:store %gx /=graph-store=/keys/noun)` will come
106into the `on-peek` arm of `%graph-store` as `/x/keys`.
106into the `on-peek` arm of `%graph-store` as `/x/keys`.
107
107
108The `on-peek` arm produces a `(unit (unit cage))`. The reason for the double
108The `on-peek` arm produces a `(unit (unit cage))`. The reason for the double
109−`unit` is that Arvo interprets `~` to mean the scry endpoint doesn't exist at
109+`unit` is that Arvo interprets `~` to mean the scry path couldn't be resolved,
110−all, and interprets `[~ ~]` to mean the endpoint exists but the requested data
110+and interprets `[~ ~]` to means it resolved to nothing. In either case the
111−does not. In either case the dotket expression which initiated the scry will
111+dotket expression which initiated the scry will crash. The `cage` will contain
112−crash. The `cage` will contain the actual data to return.
112+the actual data to return.
113
113
114An ordinary `on-peek` arm, therefore, begins like so:
114An ordinary `on-peek` arm, therefore, begins like so:
115
115