From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Naming FCRs
Date: Mon, 27 Dec 2021 08:33:02 +0100 [thread overview]
Message-ID: <YclsLj2/MOnoXW/r@tuxteam.de> (raw)
In-Reply-To: <jwv7dbqem7r.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-12-27 7:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 22:04 Naming FCRs Stefan Monnier
2021-12-26 22:29 ` Dmitry Gutov
2021-12-27 18:55 ` Stefan Monnier
2021-12-28 0:31 ` Dmitry Gutov
2021-12-27 0:46 ` Bob Rogers
2021-12-28 13:11 ` xenodasein--- via Emacs development discussions.
2021-12-29 16:33 ` Lars Ingebrigtsen
2022-01-04 20:31 ` Stefan Monnier
2022-01-11 3:25 ` Filipp Gunbin
2022-01-11 3:44 ` Stefan Monnier
2022-01-12 4:56 ` Richard Stallman
2022-01-12 15:10 ` Stefan Monnier
2021-12-27 1:35 ` Po Lu
2021-12-27 2:33 ` Qiantan Hong
2021-12-27 4:12 ` Stefan Monnier
2021-12-27 7:33 ` tomas [this message]
2021-12-29 1:09 ` Phil Sainty
2021-12-28 4:19 ` Richard Stallman
2021-12-28 5:43 ` Po Lu
2021-12-28 11:24 ` Andreas Schwab
2021-12-28 17:28 ` Stefan Monnier
2021-12-30 10:35 ` Andreas Schwab
2021-12-27 4:15 ` Richard Stallman
2021-12-27 5:46 ` LdBeth
2021-12-27 19:48 ` Stefan Monnier
2021-12-27 4:38 ` Jim Porter
[not found] ` <jwvczlheu3o.fsf-monnier+emacs@gnu.org>
2021-12-28 18:35 ` Jim Porter
2021-12-29 1:02 ` Phil Sainty
2021-12-29 16:19 ` Richard Stallman
2021-12-29 16:43 ` [External] : " Drew Adams
2021-12-29 19:01 ` Stefan Monnier
2021-12-30 2:54 ` LdBeth
2021-12-30 4:28 ` Richard Stallman
2021-12-30 8:43 ` tomas
2021-12-30 10:15 ` Tomas Hlavaty
2021-12-30 14:00 ` Stefan Monnier
2021-12-30 18:46 ` Tomas Hlavaty
2021-12-31 4:26 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YclsLj2/MOnoXW/r@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).