From 591c19b9a91310c0ffaf767324b34d876e192698 Mon Sep 17 00:00:00 2001 From: Yaseen Date: Fri, 25 Feb 2022 18:27:54 -0500 Subject: [PATCH] story: rename generators --- pkg/arvo/gen/hood/{story-set.hoon => story-write.hoon} | 0 pkg/arvo/gen/{story-log.hoon => story-read.hoon} | 8 ++++---- 2 files changed, 4 insertions(+), 4 deletions(-) rename pkg/arvo/gen/hood/{story-set.hoon => story-write.hoon} (100%) rename pkg/arvo/gen/{story-log.hoon => story-read.hoon} (96%) diff --git a/pkg/arvo/gen/hood/story-set.hoon b/pkg/arvo/gen/hood/story-write.hoon similarity index 100% rename from pkg/arvo/gen/hood/story-set.hoon rename to pkg/arvo/gen/hood/story-write.hoon diff --git a/pkg/arvo/gen/story-log.hoon b/pkg/arvo/gen/story-read.hoon similarity index 96% rename from pkg/arvo/gen/story-log.hoon rename to pkg/arvo/gen/story-read.hoon index 0fb75df52..15a8a7419 100644 --- a/pkg/arvo/gen/story-log.hoon +++ b/pkg/arvo/gen/story-read.hoon @@ -20,19 +20,19 @@ =/ current-tako .^(tako:clay %cs /(scot %p our)/[desk]/(scot cas)/tako/~) =/ current-yaki .^(yaki:clay %cs /(scot %p our)/[desk]/(scot cas)/yaki/(scot %uv current-tako)) :- %tang -(story-log [our desk cas] current-yaki tale) +(story-read [our desk cas] current-yaki tale) :::: :: Remarks: :: -:: There are two recursions in the log file: +:: There are two recursions in the logging process: :: 1. the outer loop, `commit-loop` which threads downwards into each commit by ancestor :: 2. the inner loop, `ancestor-loop`, which threads left-to-right on reverse-ancestors :: -:: +story-log outputs a tang with the least-recent commits at the head of the list, +:: +story-read outputs a tang with the least-recent commits at the head of the list, :: even though we want most-recent commits to end up printing first. :: But because dojo prints tangs in reverse, we don't flop the results :::: -++ story-log +++ story-read |= [[our=ship syd=^desk cas=case] current-commit=yaki:clay tale=story] ^- tang %- head :: result from state