Skip to content

Minor tutorial fixes 201608a #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
facundominguez merged 4 commits into from
Aug 21, 2016
Merged

Minor tutorial fixes 201608a #26

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4ccd1c5
Minor grammar fixes
vertexcite Aug 21, 2016
17bf571
Add a delay to second example
vertexcite Aug 21, 2016
753d744
Fixed sentence to make sense
vertexcite Aug 21, 2016
5557618
Minor grammar fix
vertexcite Aug 21, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions tutorials/1ch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,9 @@ main = do
-- Die immediately - throws a ProcessExitException with the given reason.
Nothing -> die "nothing came back!"
Just s -> say $ "got " ++ s ++ " back!"

-- Without the following delay, the process sometimes exits before the messages are exchanged.
liftIO $ threadDelay 2000000
{% endhighlight %}

Note that we've used `receiveWait` this time around to get a message.
Expand Down Expand Up @@ -198,7 +201,7 @@ not depend on any runtime arguments). The type of static actions in Cloud
Haskell is `Closure (Process a)`. More generally, a value of type `Closure b`
is a value that was constructed explicitly as the composition of symbolic
pointers and serializable values. Values of type `Closure b` are serializable,
even if values of type `b` might not. For instance, while we can't in general
even if values of type `b` might not be. For instance, while we can't in general
send actions of type `Process ()`, we can construct a value of type `Closure
(Process ())` instead, containing a symbolic name for the action, and send
that instead. So long as the remote end understands the same meaning for the
Expand All @@ -218,7 +221,7 @@ For curried functions, you'll need to uncurry them first (i.e. "tuple up" the
arguments). However, to ensure that the remote side can adequately interpret
the resulting `Closure`, you'll need to add a mapping in a so-called *remote
table* associating the symbolic name of a function to its value. Processes can
only be successfully spawned on remote nodes of all these remote nodes have
only be successfully spawned on remote nodes if all these remote nodes have
the same remote table as the local one.

We need to configure our remote table (see the [API reference][6] for
Expand Down Expand Up @@ -278,8 +281,8 @@ In the above example, we spawn `sampleTask` on node `us` in two
different ways:

* using `spawn`, which expects some node identifier to spawn a process
on along for the action of the process.
* using `spawnLocal`, a specialization of `spawn` to the case when the
on along with a `Closure` for the action of the process.
* using `spawnLocal`, a specialization of `spawn` for the case when the
node identifier actually refers to the local node (i.e. `us`). In
this special case, no serialization is necessary, so passing an
action directly rather than a `Closure` works just fine.
Expand Down