bug#66554: [PATCH] Add the public API of Compat to the core

[Eli Zaretskii]

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: mail@daniel-mendler.de,  66554@debbugs.gnu.org,  stefankangas@gmail.com,
>   monnier@iro.umontreal.ca
> Date: Wed, 07 Feb 2024 17:15:45 +0000
> 
> >> Let me try to make my point more clear: I'd prefer that the reader
> >> emerges from reading this description with a practical way of knowing
> >> when to call the function directly and when to call it via
> >> 'compat-call'.  If that's not easy to understand, perhaps we should
> >> tell that 'compat-call' should always be used, to avoid some rare
> >> corner cases where a direct call will not do, and be done?
> >
> > I don't think we should recommend always using `compat-call', that would
> > make code unreadable.  What definitions have to be called via
> > `compat-call' really depends on how they were defined in Compat.  I
> > don't know of a better rule to describe it without copying the
> > documentation from the Compat manual (that wouldn't be a good idea
> > either, because it wouldn't stay up to date).
> 
> Daniel, do have any ideas how to improve the documentation here?  It
> seems to me that the authoritative source of information on what
> functions to compat-call is Compat itself, right?

What does Compat manual say about this aspect?