[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#69387: 30.0.50; A string shouldn't be both a docstring and a return
From: |
Mattias Engdegård |
Subject: |
bug#69387: 30.0.50; A string shouldn't be both a docstring and a return value |
Date: |
Mon, 26 Feb 2024 20:06:00 +0100 |
26 feb. 2024 kl. 19.17 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
> No, I mean that we should not keep the old dual-use semantics, even if
> it means some docstrings get temporarily "lost" until the code is fixed.
Yes, that's fine. Those aren't likely to have many avid readers.
> As for whether (defun (ARGS) "string") should treat the string as
> a docstring or a return value, I'd rather keep it as a return value, so
> it's the same as for `lambda`. Another reason is because, the kind of
> failures it is likely to introduce is a lot more mild: it's much safer
> to remove a docstring than to change the return value.
I agree. I'll make a patch for the warning, just so that we can see what it
would look like.
And will let you worry about the highlighting then!