Re: Distinguishing `consp` and `functionp`

[Stefan Monnier]

>> It's got several rough edges (most importantly that
>> `byte-code-function-p` returns non-nil for interpreted function values),
>> but it seems to work OK so far.
>
> Forgive me if this is noise (i.e. if that is already intended to be fixed):
> If that were not fixed, it would break a few things in non-core packages
> that I'm aware of.

Yes, clearly it can't fly without fixing that first :-)


        Stefan