[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50965: Allow nil third argument for mapconcat
|
From: |
Stefan Kangas |
|
Subject: |
bug#50965: Allow nil third argument for mapconcat |
|
Date: |
Sat, 2 Oct 2021 22:12:32 +0200 |
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I think that makes sense -- SEPARATOR is optional in the related
>
> (string-join strings &optional separator)
>
> function.
Aha, so an explicit nil third argument is already treated as the empty string:
(mapconcat #'identity '("foo" "bar") nil)
This is the case also in 27.2.
- bug#50965: Allow nil third argument for mapconcat, Stefan Kangas, 2021/10/02
- bug#50965: Allow nil third argument for mapconcat, Lars Ingebrigtsen, 2021/10/02
- bug#50965: Allow nil third argument for mapconcat,
Stefan Kangas <=
- bug#50965: Allow nil third argument for mapconcat, Stefan Kangas, 2021/10/02
- bug#50965: Allow nil third argument for mapconcat, Eli Zaretskii, 2021/10/03
- bug#50965: Allow nil third argument for mapconcat, Stefan Kangas, 2021/10/03
- bug#50965: Allow nil third argument for mapconcat, Eli Zaretskii, 2021/10/05
- bug#50965: Allow nil third argument for mapconcat, Stefan Kangas, 2021/10/05