-
Notifications
You must be signed in to change notification settings - Fork 58
deduplicates vane interfaces (+note/+sign) #1178
Conversation
d6b5119
to
f200138
Compare
$>(%look task) :: set ethereum source | ||
== :: | ||
$: @tas :: | ||
$% $>(%init vane-task) :: report install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this formatting is inconsistent with the rest
{$this p/? q/clip:eyre r/httq:eyre} :: eyre: in request | ||
{$thud ~} :: eyre: in cancel | ||
{$wake ~} :: behn: wakeup | ||
+$ unix-task :: input from unix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be nice to define vane interfaces in terms of this, rather than the other way around. That way you could look at a vane interface and immediately see which moves come from Unix. Could be done in a different PR, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovin' it
This PR uses
$>
(fixed in #1176) to deduplicate the+note
(outgoing "request") and+sign
(incoming "response") interfaces of all the vanes, defining these interfaces in terms of the+task
(incoming "request") and+gift
(outgoing "response") interfaces of other vanes wherever possible.I've also moved all the
+note
/+sign
definitions into the vanes themselves -- some were previously in %zuse, but there's no reason for anything but the vanes (and their tests) to reference these.