[latex3-commits] [git/LaTeX3-latex3-latex3] master: justify cs_set_nopar:Npx (4a4928eff)

[Joseph Wright]

Repository : https://github.com/latex3/latex3
On branch  : master
Link       : https://github.com/latex3/latex3/commit/4a4928effc356b72001095e16a2c6852485a8b67

>---------------------------------------------------------------

commit 4a4928effc356b72001095e16a2c6852485a8b67
Author: Jonathan Spratte <jspratte at yahoo.de>
Date:   Tue Aug 4 16:30:27 2020 +0200

    justify cs_set_nopar:Npx


>---------------------------------------------------------------

4a4928effc356b72001095e16a2c6852485a8b67
 l3kernel/l3keys.dtx | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/l3kernel/l3keys.dtx b/l3kernel/l3keys.dtx
index 3d5a1ea96..53eafcbbb 100644
--- a/l3kernel/l3keys.dtx
+++ b/l3kernel/l3keys.dtx
@@ -1584,7 +1584,10 @@
 %   }
 %   Searching for a property means finding the last |.| in the input,
 %   and storing the text before and after it. Everything is turned into
-%   strings, so there is no problem using an \texttt{x}-type expansion.
+%   strings, so there is no problem using an \texttt{x}-type expansion. Since
+%   |\__keys_trim_spaces:n| will turn its argument into a string anyway, this
+%   function uses \cs{cs_set_nopar:Npx} instead of \cs{tl_set:Nx} to gain some
+%   speed.
 %    \begin{macrocode}
 \cs_new_protected:Npn \@@_property_find:n #1
   {