SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Arthur A. Gleckler
(16 Jul 2020 06:10 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Panicz Maciej Godek
(16 Jul 2020 08:29 UTC)
|
||
(missing)
|
||
Fwd: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Felix Thibault
(16 Jul 2020 10:20 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Arthur A. Gleckler
(16 Jul 2020 15:07 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Duy Nguyen
(16 Jul 2020 10:11 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Arthur A. Gleckler
(16 Jul 2020 15:03 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher Marc Nieper-Wißkirchen (17 Jul 2020 09:56 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Felix Thibault
(17 Jul 2020 11:34 UTC)
|
||
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher
Marc Nieper-Wißkirchen
(17 Jul 2020 11:47 UTC)
|
Re: SRFI 204: Wright-Cartwright-Shinn Pattern Matcher Marc Nieper-WiÃkirchen 17 Jul 2020 09:56 UTC
(1) One section is called "Procedures" but it seems that syntax is described. (2) Is it intended that the syntax described in this SRFI is being packaged in an R7RS library "(srfi 204)"? It would be very helpful to clarify what this library would export. In particular, it should export all the symbols _, quote, $, struct, @, object, =, and, or, not, ?, set!, get!, quasiquote, ..., ___, ..1, ..=, ..* bound to their usual meaning or (if there is none) bound to some auxiliary syntax to preserve the spirit of R6RS and R7RS when it comes to auxiliary keywords and to be able to preserve hygiene. (3) The slot names for records cannot fully work portably if a record type has two slots with the same name (as a symbol). If a matching pattern against record getter procedures were added, it would always work (and also hygienically). Marc Am Do., 16. Juli 2020 um 08:10 Uhr schrieb Arthur A. Gleckler <xxxxxx@speechcode.com>: > > Scheme Request for Implementation 204, > "Wright-Cartwright-Shinn Pattern Matcher," > by Felix Thibault, > is now available for discussion. > > Its draft and an archive of the ongoing discussion are available at https://srfi.schemers.org/srfi-204/. > > You can join the discussion of the draft by filling out the subscription form on that page. > > You can contribute a message to the discussion by sending it to xxxxxx@srfi.schemers.org. > > Here's the abstract: > > Pattern matching is a way of decomposing a compound data structure into its component parts and assigning those parts to variables. This SRFI describes a pattern-matching library which is already in use by several scheme implementations which is able to match many common compound data structures. > > Regards, > > > SRFI Editor