You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the reasons (\verb|:normal|, \verb|:shutdown|, \verb|{:shutdown, _}|) expected from a well behaved \verb|GenServer| are not defined by \verb|GenServer|, but by either Erlang (\verb|:normal|) or the \verb|Supervisor| module.
Copy file name to clipboardExpand all lines: getting-started/mix-otp/genserver.markdown
+1-1
Original file line number
Diff line number
Diff line change
@@ -322,7 +322,7 @@ So far we have used three callbacks: `handle_call/3`, `handle_cast/2` and `handl
322
322
323
323
Since any message, including the ones sent via `send/2`, go to `handle_info/2`, there is a chance unexpected messages will arrive to the server. Therefore, if we don't define the catch-all clause, those messages could cause our registry to crash, because no clause would match. We don't need to worry about such cases for `handle_call/3` and `handle_cast/2` though. Calls and casts are only done via the `GenServer` API, so an unknown message is quite likely a developer mistake.
324
324
325
-
To help developers remember the differences between call, cast and info, the supported return values and more, we have a tiny [GenServer cheat sheet](https://raw.githubusercontent.com/elixir-lang/elixir-lang.github.com/master/cheatsheets/gen-server.pdf), and it comes with `tex`/`tikz` source.
325
+
To help developers remember the differences between call, cast and info, the supported return values and more, we have a tiny [GenServer cheat sheet](/cheatsheets/gen-server.pdf), and it comes with `tex`/`tikz` source.
0 commit comments