(missing)
(missing)
(missing)
Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Marc Nieper-Wißkirchen (06 Mar 2019 10:12 UTC)
Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Ciprian Dorin Craciun (11 Mar 2019 13:27 UTC)

Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Ciprian Dorin Craciun 11 Mar 2019 13:27 UTC

On Mon, Mar 11, 2019 at 3:19 PM Lassi Kortela <xxxxxx@lassi.io> wrote:
>  > As hinted in the previous paragraph: what would be the actual
>  > usefulness of such partial signatures? How would you use them?
>
> I would have these immediate uses for them:
>
> 3) Search for procedures by argument name. This would not be perfect
> by any means, but it's one more tool to help find procedures and could
> be implemented with almost no extra work from the index.

I think you'll be out of luck as I bet most of the times the name of
the parameter is more a hint to its actual type than anything else...

For example in case of SRFI-1, I don't remember seeing more than a
couple of instances where the parameter didn't have a generic name as
`list` or `value`...

>  > Also in case of `list-copy` I clearly want to markup that a circular
>  > list would raise an error:
>
> That sounds quite advanced :) Is there a circular list detector?

In general it can easily be implemented (while recursing over the
inputs) by using something like:

  https://en.wikipedia.org/wiki/Cycle_detection#Floyd's_Tortoise_and_Hare

Ciprian.