From: Yawar Amin <yawar.amin@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Determining compatibility for evolving programming interfaces
Date: Mon, 4 Jan 2021 11:07:56 -0500 [thread overview]
Message-ID: <CAJbYVJKvr0uggz16EU6pVO-NGZj6pXz7_3at-4DEsXrzOVBNyg@mail.gmail.com> (raw)
In-Reply-To: <101ac12b-89c3-4803-6fcb-288949a164cd@web.de>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
In general this is very difficult, because of 'module type of' and
functors. Almost any change can be a breaking change. If we pretend that
those two don't exist then we can make a modest set of guarantees. See
https://inbox.ocaml.org/caml-list/71ff7d61-6899-9b05-4c01-3984d47698ca@cea.fr/t/#u
for
more on this.
Regards,
Yawar
On Sat, Jan 2, 2021 at 2:51 AM Markus Elfring <Markus.Elfring@web.de> wrote:
> Hello,
>
> OCaml is also an instance of a programming language where type inference
> belongs
> to core functionality. The usage of various data types will evolve in
> several
> programming interfaces.
>
> * How do you think about to check if API revisions are still compatible
> there?
>
> * Which kind of variations can be occasionally tolerated in interface
> descriptions?
>
>
> I would appreciate your advices.
>
> Regards,
> Markus
>
[-- Attachment #2: Type: text/html, Size: 1331 bytes --]
prev parent reply other threads:[~2021-01-04 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 7:50 Markus Elfring
2021-01-04 6:05 ` Malcolm Matalka
2021-01-04 7:59 ` Fabrice Le Fessant
2021-01-04 16:07 ` Yawar Amin [this message]
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=CAJbYVJKvr0uggz16EU6pVO-NGZj6pXz7_3at-4DEsXrzOVBNyg@mail.gmail.com \
--to=yawar.amin@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).