Email list hosting service & mailing list manager

Existing binding forms Wolfgang Corcoran-Mathe (03 Jul 2020 16:38 UTC)
Re: Existing binding forms Panicz Maciej Godek (03 Jul 2020 20:15 UTC)
Re: Existing binding forms Marc Nieper-Wißkirchen (03 Jul 2020 21:11 UTC)
Re: Existing binding forms Panicz Maciej Godek (04 Jul 2020 06:12 UTC)
Re: Existing binding forms Wolfgang Corcoran-Mathe (04 Jul 2020 00:12 UTC)
Re: Existing binding forms Panicz Maciej Godek (04 Jul 2020 06:32 UTC)
Re: Existing binding forms Wolfgang Corcoran-Mathe (04 Jul 2020 13:39 UTC)

Existing binding forms Wolfgang Corcoran-Mathe 03 Jul 2020 16:37 UTC

I think this SRFI could avoid a great deal of confusion and
implementation difficulty by specifying separate pattern-matching
binding forms, instead of extending Scheme's core forms.

As the Rationale notes, the match-lambda, match-let, etc. forms
described in Wright's original paper are well-known and widely
implemented.  Why not specify these forms, using Wright's extensive
specification as a basis, and describe any new extensions in terms
of them?

In addition, it says in the Rationale that "[the match-lambda, etc.]
forms usually do not take into account the ability of Scheme
procedures to return multiple values".  Wright's forms do, however;
he writes of match-let: "These forms are convenient for destructuring
the result of a function that returns multiple values" (p. 1)  I'd
suggest that the author amend the rationale to indicate how this
SRFI's approach to multiple values differs from that of Wright's
forms.

Regards,

--
Wolfgang Corcoran-Mathe  <xxxxxx@sigwinch.xyz>

"Invent and fit; have fits and reinvent!" --Alan J. Perlis