From: Andrea Corallo <acorallo@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: feature/type-hierarchy 8a63e50036f 1/5: * Define 'cl--type-hierarchy' and compute 'cl--typeof-types' from it
Date: Mon, 04 Mar 2024 04:24:06 -0500 [thread overview]
Message-ID: <yp15xy2z6x5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvttlnaw09.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 03 Mar 2024 15:42:55 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>>>> The original was inconsistent on this,
>>>>> Maybe that was an oversight.
>>>>> Do you remember which inconsistency you had noticed in this respect?
>>>> I remember (symbol-with-pos symbol atom) (symbol atom), there might have
>>>> been others.
>>> I think I see. By "leaf" I really meant "non abstract": both `symbol`
>>> and `symbol-with-pos` describe *the* type of some objects (IOW `type-of`
>>> can return that symbol), as opposed to things like `sequence`, `list`,
>>> atom`, `number-or-marker`, ...
>> Ah! Mmmh then is not so simple...
>
> It's not complicated either, but I guess what you mean is that the DAG
> doesn't have enough info, and there I can I agree (which is why in the
> previous code we generated the DAG from `cl--typeof-types` instead of
> the reverse 🙂).
My 2 cents. I see `cl--typeof-types` for the nature of its non trivial
format and caveats as an internal representation that was layout-ed like
it is for some specific internal machinery. I find more convenient how
we can express the DAG now (and generate `cl--typeof-types`
automatically from it).
Andrea
next prev parent reply other threads:[~2024-03-04 9:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170801660982.26727.13226947668211497607@vcs2.savannah.gnu.org>
[not found] ` <20240215170330.82819C0F009@vcs2.savannah.gnu.org>
2024-03-01 16:49 ` feature/type-hierarchy 8a63e50036f 1/5: * Define 'cl--type-hierarchy' and compute 'cl--typeof-types' from it Stefan Monnier
2024-03-01 18:12 ` Andrea Corallo
2024-03-01 18:59 ` Stefan Monnier
2024-03-03 8:51 ` Andrea Corallo
2024-03-03 14:21 ` Stefan Monnier
2024-03-03 18:34 ` Andrea Corallo
2024-03-03 20:41 ` Stefan Monnier
2024-03-04 9:16 ` Andrea Corallo
2024-03-04 15:37 ` Stefan Monnier
2024-03-04 16:12 ` Andrea Corallo
2024-03-04 16:35 ` Stefan Monnier
2024-03-03 16:56 ` Andrea Corallo
2024-03-03 17:31 ` Stefan Monnier
2024-03-03 18:05 ` Andrea Corallo
2024-03-03 18:20 ` Stefan Monnier
2024-03-03 18:37 ` Andrea Corallo
2024-03-03 20:42 ` Stefan Monnier
2024-03-04 9:24 ` Andrea Corallo [this message]
2024-03-04 15:51 ` Stefan Monnier
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=yp15xy2z6x5.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).