Finalizing SRFI 243: Unreadable Data
Lassi Kortela
(13 Jun 2023 18:51 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Marc Nieper-Wißkirchen
(13 Jun 2023 19:35 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Lassi Kortela
(13 Jun 2023 19:59 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Marc Nieper-Wißkirchen
(15 Jun 2023 14:43 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Daphne Preston-Kendal
(13 Jun 2023 20:11 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Lassi Kortela
(13 Jun 2023 20:37 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data Marc Nieper-Wißkirchen (13 Jun 2023 20:57 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Lassi Kortela
(13 Jun 2023 21:17 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Lassi Kortela
(13 Jun 2023 21:32 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Marc Nieper-Wißkirchen
(14 Jun 2023 06:06 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Lassi Kortela
(13 Jun 2023 21:00 UTC)
|
Re: Finalizing SRFI 243: Unreadable Data
Marc Nieper-Wißkirchen
(14 Jun 2023 16:18 UTC)
|
Am Di., 13. Juni 2023 um 22:37 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>: > > > This entire idea was a non-starter, in my view. > > The alternatives were to withdraw it or make the best of it. > > I like the result, but it's clearly more in the "basic research / long > term evolution" category than something that's useful today. RnRS should > address concerns like this though. > > Basically this solves a longstanding inconsistency in the `write` > procedure. `write` wrote a self-consistent data structure in all cases > except when it's fed unreadable objects. An implementation using > stand-in objects can guarantee self-consistent output in all cases. The principal domain of the write procedure are datum objects, which possess a written representation. As long as one does not use write outside this domain, nothing is inconsistent and write works as intended (namely for textual exchange of datum objects). What is the precise definition of "self-consistent"? [...]