[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: obnoxious byte-compiler warning from using lsh
From: |
Eli Zaretskii |
Subject: |
Re: obnoxious byte-compiler warning from using lsh |
Date: |
Fri, 08 Sep 2023 14:52:26 +0300 |
> From: Noah Friedman <noah@splode.com>
> Date: Fri, 08 Sep 2023 03:26:09 -0700 (PDT)
>
> The the master branch, the docstring for `lsh' says:
>
> This function is provided for compatibility. In new code, use `ash'
> instead."
>
> `lsh' and `ash' are not the same thing, the difference is important and
> they are both essential operators. This proffered suggestion, along with
> the byte compiler warning, is...well, it's not even wrong. It's just a
> non-sequitur.
We are aware that ash and lsh are not the same, but we still want to
urge people to use ash, since in our experience most uses of lsh are
mistakes.
If you have a real-life use case where using ash simply isn't going to
work, please describe it.
Thanks.