Generative and nongenerative record types Marc Nieper-Wißkirchen (30 Oct 2022 09:09 UTC)
|
Re: Generative and nongenerative record types
John Cowan
(30 Oct 2022 16:37 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(30 Oct 2022 16:57 UTC)
|
Re: Generative and nongenerative record types
John Cowan
(30 Oct 2022 22:20 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(31 Oct 2022 09:12 UTC)
|
Re: Generative and nongenerative record types
Marc Feeley
(31 Oct 2022 12:00 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(31 Oct 2022 12:37 UTC)
|
Re: Generative and nongenerative record types
Marc Feeley
(31 Oct 2022 13:21 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(02 Nov 2022 13:09 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(02 Nov 2022 14:57 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(03 Nov 2022 19:20 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(08 Nov 2022 16:23 UTC)
|
Re: Generative and nongenerative record types
Daphne Preston-Kendal
(08 Nov 2022 16:24 UTC)
|
Re: Generative and nongenerative record types
Marc Nieper-Wißkirchen
(08 Nov 2022 16:29 UTC)
|
95% or more of the record-type definitions in practice are supposed to be nongenerative. The R6RS syntax, however, makes generative record-type definitions the default and needs an extra clause (nongenerative) to override this default. We can change the R6RS version of `define-record-type' in SRFI 237 so that non-generativity becomes the default. For the few cases, generative record types are needed, a clause (nongenerative #f) must be added. The SRFI 9 version of `define-record-type' would still create generative record types. We can't change this in SRFI 237 unless we want to abandon R7RS Small compatibility (slightly). What do you think?