On Sun, May 19, 2019 at 1:38 PM Yaron Minsky <[email protected]> wrote:
> Yeah, I've heard that mentioned before. I'm curious what notion of > compatibility it checks. Forwards, backwards, or both? e.g., does it > flag the lack of forwards compatibility for retroactive unionization? > SchemaLoader only tries to determine whether one schema is a valid "upgrade" from another, essentially checking the rules documented at: https://capnproto.org/language.html#evolving-your-protocol I actually don't remember if it allows retroactive unionization. There are definitely some types of changes that are situationally safe and which I've made in real systems which SchemaLoader would reject. -Kenton -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/CAJouXQk%3D-4Z5mx5C5Ug9-oxTgXZvecFrTyXVomicpCMAowrWfA%40mail.gmail.com.
