summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJosé Valim <jose.valim@gmail.com>2018-04-28 23:53:02 +0800
committerGitHub <noreply@github.com>2018-04-28 23:53:02 +0800
commite8b080603145472fe661ac7e2cbc91fb14bf5aed (patch)
tree8fae79110e5c569079daa8950f384091ca00847c
parent5e987a702bb5b3b06910dfc50bdb95dc21a5a9db (diff)
downloadelixir-e8b080603145472fe661ac7e2cbc91fb14bf5aed.tar.gz
Improve processes feedback in library guidelines
-rw-r--r--lib/elixir/pages/Library Guidelines.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/elixir/pages/Library Guidelines.md b/lib/elixir/pages/Library Guidelines.md
index d759c16cb..71e4b9916 100644
--- a/lib/elixir/pages/Library Guidelines.md
+++ b/lib/elixir/pages/Library Guidelines.md
@@ -235,7 +235,7 @@ def subtract(a, b) do
end
```
-If you don't need a process, then you don't need a process. Use processes only to model runtime properties, never for code organization.
+Use processes only to model runtime properties, never for code organization. And even when you think something could be done in parallel with processes, often it is best to let the callers of your library decide how to paralleiize, rather than impose a certain execution flow in users of your code.
### Avoid spawning unsupervised processes