From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: [External] : Emacs object type hierarchy
Date: Tue, 24 Oct 2023 11:32:50 +0200 [thread overview]
Message-ID: <87ttqgl60t.fsf@dataswamp.org> (raw)
In-Reply-To: yp1il6wjtxn.fsf@fencepost.gnu.org
Andrea Corallo wrote:
> I don't think so, OTOH new code could make use of it easily
> and reliably instead of having to reverse engineer the
> current implementation.
One thing I think of immediately is if one could automatically
verify the type system by the way it is constructed and the
types' associated checkers, which would be the the predicate
functions, e.g. `listp', `stringp' and so on, and see if they
can all traverse their parts of the data structure
without fail.
And if it fails to verify it would be interesting to examine
where the problem appeared, and what was to blame, the
definition/relations or the typechecks ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-10-24 9:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 8:44 Emacs object type hierarchy Andrea Corallo
2023-10-22 9:08 ` Gerd Möllmann
2023-10-22 9:37 ` Gerd Möllmann
2023-10-23 15:08 ` Andrea Corallo
2023-10-23 16:36 ` Gerd Möllmann
2023-10-23 16:48 ` Gerd Möllmann
2023-10-24 8:28 ` Andrea Corallo
2023-10-22 16:11 ` [External] : " Drew Adams
2023-10-24 0:57 ` Richard Stallman
2023-10-24 2:03 ` Emanuel Berg
2023-10-24 8:39 ` Andrea Corallo
2023-10-24 9:32 ` Emanuel Berg [this message]
2023-10-22 22:08 ` Yuan Fu
2023-10-23 15:06 ` Andrea Corallo
2023-10-23 15:49 ` John Yates
2023-10-24 3:37 ` Yuan Fu
2023-10-23 15:20 ` Andrea Corallo
2023-10-23 15:46 ` Eli Zaretskii
2023-10-24 9:21 ` Andrea Corallo
2023-10-24 11:55 ` Eli Zaretskii
2023-10-24 12:02 ` Andrea Corallo
2023-10-24 12:53 ` Emanuel Berg
2024-02-15 17:28 ` Andrea Corallo
2024-02-15 17:40 ` Andrea Corallo
2024-02-17 9:04 ` Emanuel Berg
2024-02-18 19:25 ` Andrea Corallo
2024-02-17 9:19 ` Eli Zaretskii
2024-02-17 9:38 ` Emanuel Berg
2024-02-17 9:41 ` Emanuel Berg
2024-02-18 19:23 ` Andrea Corallo
2024-02-18 19:33 ` Eli Zaretskii
2024-02-18 19:37 ` Eli Zaretskii
2024-02-19 7:52 ` Andrea Corallo
2024-02-19 16:51 ` Andrea Corallo
2024-02-26 17:50 ` Andrea Corallo
2024-03-01 8:36 ` Andrea Corallo
2024-03-01 8:56 ` Eli Zaretskii
2024-03-01 9:46 ` Andrea Corallo
2024-02-16 20:31 ` Basil L. Contovounesios
2024-02-18 19:14 ` Andrea Corallo
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=87ttqgl60t.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).