[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: |
Fri, 08 Sep 2023 11:52:25 -0400 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) |
>> This isn't backwards compatible, is it?
> Neither is what you propose, AFAIU. We are in effect changing a
> public API in incompatible ways.
Yup, AFAICT there's no way to implement the Texinfo-documented
behavior reliably.
So some backward-incompatibility is inevitable, unless we decide to
stick to the current code to be "bug compatible" :-(
Stefan
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Joseph Turner, 2023/09/07
- bug#65797: 29.0.92; func-arity should not return (0 . many) with apply-partially, Mattias Engdegård, 2023/09/07
- 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, Stefan Monnier, 2023/09/07
- 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, 2023/09/12
bug#65797: `buffer-match-p` should not use `func-arity`, Philip Kaludercic, 2023/09/08