Re: [Caml-list] How to rename a record field

[Enrico Tassi <enrico.tassi@inria.fr>]

On Thu, Sep 06, 2018 at 10:17:25PM +0900, Jacques Garrigue wrote:
> Records being the dual of variants, all the arguments apply.
> Namely, if the name is allowed to change, field access can no longer
> be seen as the intuitive projection (by name rather than position, since
> only name information is available in the source code).
> Field name disambiguation works in the same way too.

Thanks. I see why in the general case this makes the source code
ambiguous.

> >  type old = { bad : int; stuff : bool }
> >  type t = old = { good : int; stuff : bool }

But in a case as simple as this one where names are either different
or occur in the same position I believe there is no ambiguity.
"stuff" would always resolve to position 2 while both
"good" and "bad" to position 1.

I'm not knowledgeable enough to follow your reasoning about GADTs.
Maybe the approach I propose is really unsound, even if I fail to get
it. Still I believe the use case (renaming + deprecating a record field)
is relevant. Any other approach (especially not requiring to patch OCaml)
would make me happy.

Best,
-- 
Enrico Tassi

-- 
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs