Email list hosting service & mailing list manager

A reference type Marc Nieper-Wißkirchen (18 Aug 2022 21:45 UTC)
Re: A reference type John Cowan (19 Aug 2022 01:36 UTC)
Re: A reference type Lassi Kortela (19 Aug 2022 10:03 UTC)
Re: A reference type Marc Nieper-Wißkirchen (19 Aug 2022 10:11 UTC)
Re: A reference type Lassi Kortela (19 Aug 2022 10:25 UTC)
Places in Scheme Marc Nieper-Wißkirchen (19 Aug 2022 10:42 UTC)
Re: Places in Scheme Marc Nieper-Wißkirchen (19 Aug 2022 11:36 UTC)
Re: Places in Scheme Per Bothner (19 Aug 2022 16:33 UTC)
Re: Places in Scheme Marc Nieper-Wißkirchen (19 Aug 2022 17:58 UTC)
Re: Places in Scheme Panicz Maciej Godek (25 Aug 2022 15:20 UTC)
Re: Places in Scheme Ray Dillinger (26 Aug 2022 02:29 UTC)
Re: A reference type Marc Nieper-Wißkirchen (19 Aug 2022 10:54 UTC)
Re: A reference type Marc Nieper-Wißkirchen (19 Aug 2022 11:44 UTC)
Re: A reference type Peter Bex (19 Aug 2022 12:02 UTC)
Re: A reference type Marc Nieper-Wißkirchen (19 Aug 2022 12:26 UTC)
Big words Lassi Kortela (19 Aug 2022 16:29 UTC)
Re: Big words Marc Nieper-Wißkirchen (19 Aug 2022 18:07 UTC)
Re: Big words Lassi Kortela (19 Aug 2022 20:06 UTC)
Re: Big words Marc Nieper-Wißkirchen (19 Aug 2022 20:31 UTC)
Re: Big words blake@xxxxxx (19 Aug 2022 22:06 UTC)
Re: Big words blake@xxxxxx (19 Aug 2022 22:08 UTC)
Re: Big words Arthur A. Gleckler (19 Aug 2022 18:09 UTC)
Re: Big words John Cowan (19 Aug 2022 18:39 UTC)

Places in Scheme Marc Nieper-Wißkirchen 19 Aug 2022 10:42 UTC

Am Fr., 19. Aug. 2022 um 12:25 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>:
>
> > See the message at
> > https://srfi-email.schemers.org/srfi-17/msg/2778561/  and the following
> > discussion for why there are good arguments against a SRFI-17-style
> > addition to Scheme.  I definitely subscribe to these arguments. Per,
> > the author of SRFI 17, does not. But we already had such a discussion
> > and continuing it should happen somewhere else.
>
> There are two distinct questions here:
>
> 1) Should set! be able to set things other than variables?
>
> 2) Should references/places be first-class or implied?
>
> By my reading, your argument is that Scheme is cleaner (from a
> functional programming standpoint?) if references/places are first class.

A locative is a first-class object.

A place would be, like a variable, not first-class.

"set!" in Scheme is syntax and does not mutate its argument (which is
some syntax) but the location which the syntactic argument references.

"set-car!" (and friends) are procedures taking a first-class
(evaluated) argument and mutating it.

It's not about that all entities should be first-class. Variables
aren't, for example.

As I don't want to repeat all arguments, let me cite one I find
compelling: https://srfi-email.schemers.org/srfi-17/msg/2778611/.