From: Yawar Amin <yawar.amin@gmail.com>
To: "François Bobot" <francois.bobot@cea.fr>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Tools for helping backward compatibility?
Date: Sat, 22 Aug 2020 00:09:02 -0400 [thread overview]
Message-ID: <CAJbYVJLnXJpc-mi=5x7wy9ZGUfafFig3hSPGihive+MNuMd7Fg@mail.gmail.com> (raw)
In-Reply-To: <71ff7d61-6899-9b05-4c01-3984d47698ca@cea.fr>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Hi,
On Fri, Aug 21, 2020 at 8:19 AM François Bobot <francois.bobot@cea.fr>
wrote:
> ...
> - Given an API, the guarantees of the possible modifications of the API,
> and a new version of the
> API: check if the new version follows the guarantees
>
Do you mean something like Semantic Versioning here? See e.g. Elm which has
a package manager that can enforce SemVer by comparing types:
https://elm-lang.org/news/0.14
> For package authors, it means we can automatically enforce semantic
versioning. No user will ever get a breaking API change in a patch version
again!
Something like this for OCaml would be very cool. But I've heard that
SemVer for OCaml is either difficult or effectively impossible, indeed due
to some of the reasons you listed. I think any practical codification of
backward-compatibility rules would probably need to ignore the presence of
features like 'module type of' and 'include'.
Regards,
Yawar
[-- Attachment #2: Type: text/html, Size: 1437 bytes --]
next prev parent reply other threads:[~2020-08-22 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 12:19 François Bobot
2020-08-21 13:52 ` Hendrik Boom
2020-08-24 9:18 ` François Bobot
2020-08-22 4:09 ` Yawar Amin [this message]
2020-08-24 8:51 ` François Bobot
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='CAJbYVJLnXJpc-mi=5x7wy9ZGUfafFig3hSPGihive+MNuMd7Fg@mail.gmail.com' \
--to=yawar.amin@gmail.com \
--cc=caml-list@inria.fr \
--cc=francois.bobot@cea.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).