a0b377d · urbit.org · git.iko.soy

git.iko.soy/urbit.org

on master help sign in

fix brackets

a0b377ddrbeefsupreme5 years ago

content/docs/userspace/threads/basics/bind.md+5−5

compare with master

unifiedsplit

@@ -34,16 +34,16 @@ j

35## bind

37−Bind by itself must be specialised like `(bind:m ,<type>)` and it takes two arguments:

37+Bind by itself must be specialised like `(bind:m ,<type>)` and it takes two arguments:

39−- The first argument is a function that returns the `form` of a strand which produces `<type>`.

39+- The first argument is a function that returns the `form` of a strand which produces `<type>`.

40−- The second argument is a gate whose sample is `<type>` and which returns a `form`.

40+- The second argument is a gate whose sample is `<type>` and which returns a `form`.

42−Since you'll invariably use it in conjunction with micgal, the `<type>` in `;< <type> bind:m ...` will both specialise `bind` and specify the gate's sample.

42+Since you'll invariably use it in conjunction with micgal, the `<type>` in `;< <type> bind:m ...` will both specialise `bind` and specify the gate's sample.

44Bind calls the first function then, if it succeeded, calls the second gate with the result of the first as its sample. If the first function failed, it will instead just return an error message and not bother calling the next gate. So it's essentially "strand A then strand B".

46−Since the second gate may itself contain another `;< <type> bind:m ...`, you can see how this allows you to glue together an arbitrarily large pipeline, where subsequent gates depend on the previous ones.

46+Since the second gate may itself contain another `;< <type> bind:m ...`, you can see how this allows you to glue together an arbitrarily large pipeline, where subsequent gates depend on the previous ones.

48## strandio

content/docs/userspace/threads/basics/output.md+1−1

@@ -4,7 +4,7 @@ weight = 4

4template = "doc.html"

5+++

7−A strand produces a `[(list card) <response>]`. The first part is a list of cards to be sent off immediately, and `<response>` is one of:

7+A strand produces a `[(list card) <response>]`. The first part is a list of cards to be sent off immediately, and `<response>` is one of:

9- `[%wait ~]`

10- `[%skip ~]`

content/docs/userspace/threads/basics/summary.md+4−4

@@ -49,8 +49,8 @@ Now here's a quick recap of the main points covered:

49#### bind

50- is used to chain strands together like javascript promises

51- is used in conjunction with micgal (`;<`)

52−- must be specialised to a type like `;< <type> bind:m ...`

52+- must be specialised to a type like `;< <type> bind:m ...`

53−- takes two arguments. The first is a function that returns the `form` of a `strand` that produces `<type>`. The second is a gate whose sample is `<type>` and which returns a `form`.

53+- takes two arguments. The first is a function that returns the `form` of a `strand` that produces `<type>`. The second is a gate whose sample is `<type>` and which returns a `form`.

54- calls the first and then, if it succeeded, calls the second with the result of the first as its sample.

56## Strand input

@@ -62,9 +62,9 @@ Now here's a quick recap of the main points covered:

63## Strand output

65−- contains `[cards=(list card:agent:gall) <response>]`

65+- contains `[cards=(list card:agent:gall) <response>]`

66- `cards` are any cards to be sent immediately

67−- `<response>` is something like `[%done value]`, `[%fail err]`, etc.

67+- `<response>` is something like `[%done value]`, `[%fail err]`, etc.

68- `%done` will contain the result

69- responses are only used internally to manage the flow of the thread and are not returned to subscribers.