[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with
From: |
Mattias Engdegård |
Subject: |
bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment |
Date: |
Sat, 23 Sep 2023 18:43:24 +0200 |
23 sep. 2023 kl. 18.08 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
>
>> - `declare` is only allowed in named definitions because it is
>> macro-expanded very early, so we have no way of annotating lambda
>> expressions
>
> It's not because of timing, it's because these `declare` all store their
> info on the symbol (and some of them even fundamentally really apply to
> the name and wouldn't make sense when applied to an anonymous function,
> e.g. obsolescence).
That is true, but some of the declarations might be useful for lambda
expressions as well, and more to the point, we don't have any other way to
annotate functions in general, only function symbols. Arguably we should invent
new syntax for whatever we need, but it would be one more thing to parse.
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/21
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/21
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/21
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Eli Zaretskii, 2023/09/22
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Stefan Monnier, 2023/09/22
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/22
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Stefan Monnier, 2023/09/22
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/22
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Mattias Engdegård, 2023/09/23
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Stefan Monnier, 2023/09/23
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment,
Mattias Engdegård <=
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Stefan Monnier, 2023/09/23
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Mattias Engdegård, 2023/09/24
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Stefan Monnier, 2023/09/24
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/23
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Stefan Monnier, 2023/09/23
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Jens Schmidt, 2023/09/25
- bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment, Mattias Engdegård, 2023/09/25