From: Sebastian Miele <sebastian.miele@gmail.com>
To: 41983@debbugs.gnu.org
Subject: bug#41983: Reference Manual: Open Question About Magic Metaness of Vtables
Date: Sun, 21 Jun 2020 16:27:43 +0200 [thread overview]
Message-ID: <87eeq8o5nk.fsf@gmail.com> (raw)
I am on the current master branch. After reading section 6.6.18.4
(Meta-Vtables) of the reference manual there remains an open question.
A structure X made from a meta-vtable becomes a meta-vtable if
standard-vtable-fields is a prefix of the layout in X's field 0. And if
X is a meta-vtable, every structure with X as a vtable must have a valid
layout in field 0.
Suppose the following: standard-vtable-fields accidentally is a prefix
of some valid layout string l. Then
(define v (make-vtable l))
(make-struct/no-tail v 'a)
raises an exception, because 'a is not a valid layout. But v may not be
intended to be a meta-vtable, just a vtable. The reference manual does
mention why that can not happen, or why is it accepted that it may
happen.
reply other threads:[~2020-06-21 14:27 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eeq8o5nk.fsf@gmail.com \
--to=sebastian.miele@gmail.com \
--cc=41983@debbugs.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).