caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "François Bobot" <francois.bobot@cea.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Tools for helping backward compatibility?
Date: Mon, 24 Aug 2020 11:18:54 +0200	[thread overview]
Message-ID: <e79d3363-1669-cabc-742b-11405cf70ec5@cea.fr> (raw)
In-Reply-To: <20200821135246.rccrpa36gyj5gasg@topoi.pooq.com>

Le 21/08/2020 à 15:52, Hendrik Boom a écrit :
> On Fri, Aug 21, 2020 at 02:19:10PM +0200, François Bobot wrote:
>> Hi all,
>>
>>   Backward compatibility helps a lot a community of packages to move forward. There are other
>> possibilities like being able to co-install multiple version of a library, but having backward
>> compatibility is still a huge simplification of the problem.
> 
> I forget if OCaml lets you specify just exactly which names you import 
> from a module.


Since https://github.com/ocaml/ocaml/pull/2147, which implements
https://www.cl.cam.ac.uk/~jdy22/papers/extending-ocamls-open.pdf it is possible to restrict easily
the names you are importing but you need to specify the type of each of them, which is quite verbose.


> But if it does, some editor features would be useful:
> 

> Yes, these changes will likely need deep interaction between the editor 
> and the compiler.

It could be fun to have the information automatically updated during the edition. The refreshing of
the precise import could also be done just once before any release.

Best,

-- 
François

  reply	other threads:[~2020-08-24  9:19 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 [this message]
2020-08-22  4:09 ` Yawar Amin
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=e79d3363-1669-cabc-742b-11405cf70ec5@cea.fr \
    --to=francois.bobot@cea.fr \
    --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).