on master help sign in
Though they are delicious, "basteries" must go
commit8cf1fb8877970c920a7be8675e67adb2ae7e0a3f authorpilfer-pandex <47340789+pilfer-pandex@users.noreply.github.com> dateSat 16 Mar 2019, 17:43 (8 years ago) parent8dea30b
1 file changed+4−4
reference/hoon-expressions/rune/sig.udon+4−4
reference/hoon-expressions/rune/sig.udon+4−4
@@ -179,11 +179,11 @@ wing `q`. We assume the parent is already registered -- as it
179179must be, if (a) we registered it on creation, (b) the child was
180180created by an arm defined on the parent.
181181
182−(Cores are actually managed by their formula/bastery. Any
182+(Cores are actually managed by their formula/battery. Any
183183function call will create a new core with a new sample, but
184−basteries are constant. But it is not sufficient to match the
185−bastery -- matching the semantics constrains the payload as well,
186−since the semantics of a bastery may depend on any parent core
184+batteries are constant. But it is not sufficient to match the
185+battery -- matching the semantics constrains the payload as well,
186+since the semantics of a battery may depend on any parent core
187187and/or payload constant.)
188188
189189The purpose of registration is always performance-related. It