aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2017-01-10 13:51:19 +0100
committerBjörn Gustavsson <[email protected]>2017-01-10 13:51:19 +0100
commit0264d301de02c5dd7b2a9a389294ea4a36127046 (patch)
treeaa05880d7436ccc233dc989823502b2959339529
parent448e8aca77dd29ed5b37d56f0700d24ac26a7243 (diff)
downloadotp-0264d301de02c5dd7b2a9a389294ea4a36127046.tar.gz
otp-0264d301de02c5dd7b2a9a389294ea4a36127046.tar.bz2
otp-0264d301de02c5dd7b2a9a389294ea4a36127046.zip
Remove paragraph mentioning improvements in R12B
-rw-r--r--system/doc/efficiency_guide/introduction.xml8
1 files changed, 0 insertions, 8 deletions
diff --git a/system/doc/efficiency_guide/introduction.xml b/system/doc/efficiency_guide/introduction.xml
index ca4a41c798..b650008ae8 100644
--- a/system/doc/efficiency_guide/introduction.xml
+++ b/system/doc/efficiency_guide/introduction.xml
@@ -46,14 +46,6 @@
to find out where the performance bottlenecks are and optimize only the
bottlenecks. Let other code stay as clean as possible.</p>
- <p>Fortunately, compiler and runtime optimizations introduced in
- Erlang/OTP R12B makes it easier to write code that is both clean and
- efficient. For example, the ugly workarounds needed in R11B and earlier
- releases to get the most speed out of binary pattern matching are
- no longer necessary. In fact, the ugly code is slower
- than the clean code (because the clean code has become faster, not
- because the uglier code has become slower).</p>
-
<p>This Efficiency Guide cannot really teach you how to write efficient
code. It can give you a few pointers about what to avoid and what to use,
and some understanding of how certain language features are implemented.