Re: Native compilation on Windows, was Re: Bootstrap Compilation Speed

[Corwin Brust]

This is looking good!  I have a few suggestions but not all will
likely interest you.

On Wed, Feb 9, 2022 at 12:23 PM H. Dieter Wilhelm
<dieter@duenenhof-wilhelm.de> wrote:
>
> I took up the idea from Alan Third and completed some missing "standard"
> features (from nt/INSTALL.W64):
>
>   (defun insert-feature (description test)

I wonder if it would be worth separating the name from the rest of the
description?  This could make the output even prettier.

in a similar vein, I think tabulated list mode could be a good fit for
this.  For the sake of argument, let's suppose the tests are moved to
an var, something like:

(defcustom list-features-list
  '((name:"Zlib"
    description:"compression library"
    test: zlib-available-p)
    ;; ... and so on
  )
  "List of optional Emacs features.

This is used by `list-features', which see.")

At this point `list-features' only has to walk the last transforming
the function to results to become suitable for use as a
"tabulated-list-entries function".

As a bonus, the "testable features list" could enable users to
customize which features should usually be tested/listed, for example
to add non-standard features (as long as they have a test in mind for
them), and to remove things they don't typically care out about per in
their own uses

Even aside putting the tests into a var, I think the sortable
header-line approach taken by tabulated-list-mode could make
`list-features' nicely consistent with, e.g. `list-processes.

>
>     ;; jansson = json?

I think we only get jason-parse-string if jannson is available, so:
  (functionp 'json-parse-string)

>     ;; thread support?

Not sure on this one, but I suspect we might be able to use:
  (functionp 'make-thread)

>     ;; modules
>     ;; gmp <- gnutls

Pretty sure this is just
  (gnutls-available-p)

>
> What do you think?
>

*I* think `list-features' is going to be very nice to have.

Please & thank you!