[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-p
From: |
Stefan Monnier |
Subject: |
bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially |
Date: |
Tue, 12 Sep 2023 14:30:45 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
>> So some backward-incompatibility is inevitable, unless we decide to
>> stick to the current code to be "bug compatible" :-(
> I think one of the alternatives you proposed was backward-compatible
> (albeit not very elegant). So my vote is for that alternative.
I'd first want to decide which semantics we want to document.
We could keep the current semantics, but since we're unable to implement it
reliably I'd rather we change it.
After that we can decide on how to preserve backward compatibility (for
which it would be OK to rely on a hack like the current one).
Maybe the simplest change is to align the Texinfo doc with the docstring
(i.e. document that two args are passed, always) and keep the code as
is. And maybe tweak the code so it emits a warning when
(eq 1 (cdr (func-arity condition)))
is true.
Stefan
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, (continued)
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Stefan Monnier, 2023/09/07
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Joseph Turner, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Eli Zaretskii, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Stefan Monnier, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Joseph Turner, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Stefan Monnier, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Joseph Turner, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Eli Zaretskii, 2023/09/08
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Joseph Turner, 2023/09/11
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Eli Zaretskii, 2023/09/11
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially,
Stefan Monnier <=
bug#65797: `buffer-match-p` should not use `func-arity`, Philip Kaludercic, 2023/09/08
- bug#65797: `buffer-match-p` should not use `func-arity`, Stefan Monnier, 2023/09/12
- bug#65797: `buffer-match-p` should not use `func-arity`, Philip Kaludercic, 2023/09/14
- bug#65797: `buffer-match-p` should not use `func-arity`, Stefan Monnier, 2023/09/14
- bug#65797: `buffer-match-p` should not use `func-arity`, Philip Kaludercic, 2023/09/18
- bug#65797: `buffer-match-p` should not use `func-arity`, Stefan Monnier, 2023/09/18
- bug#65797: `buffer-match-p` should not use `func-arity`, Philip Kaludercic, 2023/09/18
- bug#65797: `buffer-match-p` should not use `func-arity`, Stefan Monnier, 2023/09/18
- bug#65797: `buffer-match-p` should not use `func-arity`, Philip Kaludercic, 2023/09/19
- bug#65797: `buffer-match-p` should not use `func-arity`, Dmitry Gutov, 2023/09/19