Re: Naming FCRs

[tomas]

On Sun, Dec 26, 2021 at 11:12:48PM -0500, Stefan Monnier wrote:

[...]

> Bob Rogers [2021-12-26 19:46:39] wrote:
> > Without looking at the code, this sounds more like a closure to me.
> 
> Right, I rarely distinguish "closures" from "functions", but indeed,
> these are more closures in that their "heap object" characteristics are
> made more visible.
> 
> > Since the slots are accessible outside the function, that would make it
> > a "transparent closure" . . . but I like the internal dissonance of
> > "open closure" better.  ;-}
> 
> I like that, thank you.

Happened to me, too... so I went out there trolling the tesauri in the
Interwebs, specifically for "antonyms of closure". The net is weird, it
has answers to such a crazy question. Loads of answers:

Some which jumped at me for different reasons:

 - opening (too generic, but...)
 - continuation (not proposing that, it's taken, but... wow ;-)
 - disclosure (that one has a nice ring to it)
 - survival (nah, but... ;-)
 - preservation
 - continuance
 - continuity
 - introduction
 - can of worms (!)

This isn't meant as direct proposals (in fact, the "continuation"
flavoured ones are dangerous, since that has a clear, different
connotation in Lispy worlds). It's rather meant as "inspiring material".
The only direct candidate I somewhat like in that list would be
"disclosure" -- I'd expect it to recall the association of "closure",
helping the user's intuition. Like a closure, but you have access to
some of its knobs from the outside.

Cool idea, BTW :)

Cheers

[1] https://thesaurus.plus/antonyms/closure
[2] https://www.wordhippo.com/what-is/the-opposite-of/closure.html
[3] https://www.powerthesaurus.org/closure/antonyms

-- 
tomás

signature.asc
Description: PGP signature