From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>,
"João Távora" <joaotavora@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Changing a cl-defstruct definition in a published package
Date: Fri, 13 Jul 2018 14:21:14 -0400 [thread overview]
Message-ID: <69d5a564-6620-3691-9fb7-d0798b817f8a@gmail.com> (raw)
In-Reply-To: <87lgaf3uk3.fsf@tcd.ie>
On 2018-07-13 13:38, Basil L. Contovounesios wrote:
> If cl-defstructs boil down to an array in disguise (I don't know because
> I've never looked into them), would appending (as opposed to prepending
> or inserting) new slots maintain backward compatibility?
I don't think so, unfortunately, because of the second issue I mentioned at the end of my email: constructors called on B's side have been compiled down to array initializations, which means that even if the new constructor for my defstruct has a default value set, B will still pass me arrays that are one element too short :/
next prev parent reply other threads:[~2018-07-13 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 20:12 Changing a cl-defstruct definition in a published package Clément Pit-Claudel
2018-07-13 17:01 ` João Távora
2018-07-13 17:38 ` Basil L. Contovounesios
2018-07-13 18:21 ` Clément Pit-Claudel [this message]
2018-07-13 18:26 ` Clément Pit-Claudel
2018-07-13 19:38 ` João Távora
2018-07-13 19:52 ` Clément Pit-Claudel
2018-07-13 20:40 ` Stefan Monnier
2018-07-13 21:07 ` Clément Pit-Claudel
2018-07-14 3:36 ` Stefan Monnier
2018-07-15 4:25 ` Clément Pit-Claudel
2018-07-15 13:11 ` Stefan Monnier
2018-07-15 13:25 ` Clément Pit-Claudel
2018-07-16 1:51 ` Stefan Monnier
2018-07-30 21:52 ` Clément Pit-Claudel
2018-07-30 22:49 ` Stefan Monnier
2018-07-31 3:28 ` Clément Pit-Claudel
-- strict thread matches above, loose matches on Subject: below --
2018-07-19 20:27 Jake
2018-07-19 21:10 ` Stefan Monnier
2018-07-19 21:34 ` Jake
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=69d5a564-6620-3691-9fb7-d0798b817f8a@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.