From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andrea Corallo <acorallo@gnu.org>
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 11:35:19 -0500 [thread overview]
Message-ID: <jwv34t67y91.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yp1sf16x9gf.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Mon, 04 Mar 2024 11:12:16 -0500")
> I see, but I'm not thinking to the content of `cl--typeof-types`. I'm
> thinking to the representation we generate for our doc with the type
> hierarchy. I'm wondering if we should include `cl--class`,
> `cl-structure-object`, `cl-structure-class` as built-in types.
I guess it would make sense to include parts of the
struct/EIEIO/OClosure hierarchy for people to understand how they fit
alongside the "builtin" part, indeed.
Stefan
next prev parent reply other threads:[~2024-03-04 16:35 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 [this message]
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
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=jwv34t67y91.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acorallo@gnu.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).