|
either-guard reference implementation
Shiro Kawai
(16 Jul 2020 02:15 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(16 Jul 2020 04:28 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(16 Jul 2020 04:42 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(16 Jul 2020 05:01 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(16 Jul 2020 15:12 UTC)
|
|
Re: either-guard reference implementation Wolfgang Corcoran-Mathe (16 Jul 2020 17:24 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(16 Jul 2020 17:45 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(16 Jul 2020 18:04 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(16 Jul 2020 18:07 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(16 Jul 2020 18:29 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(16 Jul 2020 23:31 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(17 Jul 2020 00:10 UTC)
|
|
Re: either-guard reference implementation
Arthur A. Gleckler
(17 Jul 2020 03:15 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(17 Jul 2020 04:27 UTC)
|
|
Re: either-guard reference implementation
Arthur A. Gleckler
(17 Jul 2020 05:00 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(17 Jul 2020 05:55 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(17 Jul 2020 05:55 UTC)
|
|
Re: either-guard reference implementation
Shiro Kawai
(17 Jul 2020 07:35 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(17 Jul 2020 13:40 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(17 Jul 2020 13:50 UTC)
|
|
Re: either-guard reference implementation
Arthur A. Gleckler
(18 Jul 2020 05:22 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(18 Jul 2020 12:32 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(29 Jul 2020 23:18 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(31 Jul 2020 08:36 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(05 Aug 2020 06:07 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(05 Aug 2020 06:22 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(05 Aug 2020 06:28 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(05 Aug 2020 06:48 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(07 Aug 2020 22:08 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(09 Aug 2020 11:14 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(09 Aug 2020 13:10 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(11 Aug 2020 08:14 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(11 Aug 2020 16:48 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(15 Aug 2020 12:11 UTC)
|
|
Re: either-guard reference implementation
John Cowan
(15 Aug 2020 13:57 UTC)
|
|
Re: either-guard reference implementation
Marc Nieper-Wißkirchen
(16 Jul 2020 20:40 UTC)
|
|
Re: either-guard reference implementation
Wolfgang Corcoran-Mathe
(16 Jul 2020 23:25 UTC)
|
On 2020-07-16 11:11 -0400, John Cowan wrote: > No trouble there A <body> is what goes inside a `let`, zero or more > definitions followed by one or more expressions. The implementation should > be changed to wrap the body in a `(let () body)`. I'm a little confused. Whether the macro wraps <body> in a lambda (as it is in the current implementation) or in a let, <body> must contain at least one expression. If this is what is expected, I think the SRFI should indicate that "<body> is a sequence of zero or more definitions followed by one or more expressions". If not, what value do we expect from (either-guard foo?) ? Left of an unspecified value? -- Wolfgang Corcoran-Mathe <xxxxxx@sigwinch.xyz> "We have lost exactly what we wanted to lose." --Fong & Spivak
