|
semantics of copy and mirror
Peter McGoron
(21 Mar 2026 17:39 UTC)
|
|
Re: semantics of copy and mirror
Daniel Ziltener
(21 Mar 2026 23:06 UTC)
|
|
Re: semantics of copy and mirror
Peter McGoron
(22 Mar 2026 00:10 UTC)
|
|
Re: semantics of copy and mirror
Daniel Ziltener
(23 Mar 2026 20:12 UTC)
|
|
Re: semantics of copy and mirror
John Cowan
(23 Mar 2026 21:03 UTC)
|
|
Re: semantics of copy and mirror Daniel Ziltener (27 Mar 2026 21:33 UTC)
|
|
Re: semantics of copy and mirror
John Cowan
(27 Mar 2026 22:12 UTC)
|
|
Re: semantics of copy and mirror
Daniel Ziltener
(27 Mar 2026 23:39 UTC)
|
|
Re: semantics of copy and mirror
John Cowan
(28 Mar 2026 00:44 UTC)
|
|
Re: semantics of copy and mirror
Daniel Ziltener
(02 Apr 2026 22:09 UTC)
|
|
Re: semantics of copy and mirror
Peter McGoron
(02 Apr 2026 22:34 UTC)
|
|
Re: semantics of copy and mirror
jobol
(24 Mar 2026 06:46 UTC)
|
|
Re: semantics of copy and mirror
Daniel Ziltener
(27 Mar 2026 21:41 UTC)
|
On 3/23/26 22:03, John Cowan wrote: > > On Mon, Mar 23, 2026 at 4:12 PM Daniel Ziltener <xxxxxx@lyrion.ch> > wrote: > > Okay. I adjusted the `copy` message doc accordingly, and added a > `deep-copy` message that is declared as optional for implementers. I > definitely won't be able to implement this in pure R7RS, nor in my > "day > to day" dialect of Chicken, but I think now that deep-copying is a > potentially valuable mechanic for some. > > > I'm not sure why it can't be implemented, given a rule that you don't > descend into arbitrary Scheme values like pairs, lists, vectors, or > records (the last being obviously problematic) Not descending into everything means it by definition is not a deep copy.