@@ -95,8 +95,8 @@ will not block the caller, even if the caller is sending messages to itself!
95
95
96
96
Receiving works the opposite way, blocking the caller until a message
97
97
matching the expected type arrives in our (conceptual) mailbox. If multiple
98
- messages of that type are present in the mailbox, they're be returned in FIFO
99
- order, if not, the caller is blocked until a message arrives that can be
98
+ messages of that type are present in the mailbox, they'll be returned in FIFO
99
+ order. If not, the caller is blocked until a message arrives that can be
100
100
decoded to the correct type.
101
101
102
102
Let's spawn two processes on the same node and have them talk to each other.
@@ -184,13 +184,13 @@ In distributed-process if `f : T1 -> T2` then
184
184
$(mkClosure 'f) :: T1 -> Closure T2
185
185
{% endhighlight %}
186
186
187
- That is, the first argument to the function we pass to mkClosure will act
187
+ That is, the first argument to the function we pass to ` mkClosure ` will act
188
188
as the closure environment for that process. If you want multiple values
189
189
in the closure environment, you must "tuple them up".
190
190
191
191
We need to configure our remote table (see the documentation for more details)
192
192
and the easiest way to do this, is to let the library generate the relevant
193
- code for us. For example (taken from the distributed-process-platform test suites) :
193
+ code for us. For example:
194
194
195
195
{% highlight haskell %}
196
196
sampleTask :: (TimeInterval, String) -> Process String
0 commit comments