lib/keyword.3, doc/concepts.tex: Mention performance of keyword arguments.

It's surprisingly not that bad.

diff --git a/doc/concepts.tex b/doc/concepts.tex
index 39dfd2eb50e80a96fc5220ad5fa3422b03c55224..6b21109d0af14f2b0a4c1e161f9d772cf0299f0b 100644 (file)
--- a/doc/concepts.tex
+++ b/doc/concepts.tex
@@ -534,6 +534,13 @@ Keyword arguments can be provided in three ways.
   call, which is useful when writing wrapper functions.
 \end{enumerate}
 
   call, which is useful when writing wrapper functions.
 \end{enumerate}
 

+Perhaps surprisingly, keyword arguments have a relatively small performance
+impact.  On the author's aging laptop, a call to a simple function, passing
+two out of three keyword arguments, takes about 30 cycles longer than calling
+a standard function which just takes integer arguments.  On the other hand,
+quite a lot of code is involved in decoding keyword arguments, so code size
+will naturally suffer.
+

 Keyword arguments are provided as a general feature for C functions.
 However, Sod has special support for messages which accept keyword arguments
 (\xref{sec:concepts.methods.keywords}); and they play an essential rôle in
 Keyword arguments are provided as a general feature for C functions.
 However, Sod has special support for messages which accept keyword arguments
 (\xref{sec:concepts.methods.keywords}); and they play an essential rôle in

diff --git a/lib/keyword.3 b/lib/keyword.3
index 0c6e3e68ef1a5b2fcad181af89dfd20dab6f9b5d..db5b86d2c487b2fa7de1c127536f02f3815e1933 100644 (file)
--- a/lib/keyword.3
+++ b/lib/keyword.3
@@ -212,6 +212,17 @@ Argument vectors are rather inconvenient to use,
 but are the only practical way in which a caller can decide at runtime
 which arguments to include in a call,
 which is useful when writing wrapper functions.
 but are the only practical way in which a caller can decide at runtime
 which arguments to include in a call,
 which is useful when writing wrapper functions.

+.PP
+Perhaps surprisingly,
+keyword arguments have a relatively small performance impact.
+On the author's aging laptop,
+a call to a simple function,
+passing two out of three keyword arguments,
+takes about 30 cycles longer than
+calling a standard function which just takes integer arguments.
+On the other hand,
+quite a lot of code is involved in decoding keyword arguments,
+so code size will naturally suffer.

 .
 .SS Type definitions
 The header file defines two simple structure types.
 .
 .SS Type definitions
 The header file defines two simple structure types.