From: Andrew MacLeod <amacleod@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "hernandez, aldy" <aldyh@redhat.com>
Subject: [TTYPE] Strongly typed tree project. Original document circa 2017
Date: Wed, 29 Nov 2023 11:16:43 -0500 [thread overview]
Message-ID: <1acd7994-2440-4092-897f-97f14d3fbf45@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On IRC today the subject of why we don't have a strongly typed class for
types rather than trees came up.
I did work on a prototype for this back in 2016/2017, but then got
sidetracked by ranger. It exists in an SVN branch and I briefly looked
at resurrecting the patches a while ago and refitting them for trunk,
but have not gotten back to it yet. I have the patches on one of my
machines too.
If there is interest, we could consider resurrecting it for GCC 15 stage
1... but regardless, I'll post the original PDF document here in case
anyone is interested in how it worked.. back then anyway.
Andrew
[-- Attachment #2: ttype-2017.pdf --]
[-- Type: application/pdf, Size: 137439 bytes --]
reply other threads:[~2023-11-29 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1acd7994-2440-4092-897f-97f14d3fbf45@redhat.com \
--to=amacleod@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.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.
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).