Re: Instead of pcase

[Emanuel Berg]

Michael Heerdegen via "Emacs development discussions." wrote:

>> Also, special forms which had a fixed meaning have now
>> become ambiguous - and and or. Again, it takes conscious
>> inspection to determine whether one of these has its
>> standard meaning, or the very different pcase meaning.
>
> So, would it help if they would be called differently, e.g.
> "pand" and "por"?

And "ror" for `rx'?

Yeah, if one is skimming the code and expects to understand
all of it from just doing that, maybe "pand" and "por" are
better. But when you are inside something, pcase in this case,
it is pretty much understood that then the rules are defined
by that, not what is outside.

Maybe the maintainers felt at some point they were 100% fluent
with Elisp just by visual inspection with no manual decoding
in the brain whatsoever, and now they feel cl-lib and pcase
has ruined that fluency.

So maybe the options are either getting as fluent with cl-lib
and pcase as well, or, if that cannot be done, accepting that
the "good old Elisp" days of total fluency is gone and it is
not coming back.

-- 
underground experts united
https://dataswamp.org/~incal