caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Simon Cruanes <simon.cruanes.2007@m4x.org>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Damien Doligez <damien.doligez@inria.fr>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml release 4.02.2
Date: Fri, 19 Jun 2015 14:08:05 +0200	[thread overview]
Message-ID: <20150619120805.GV32363@emmental.inria.fr> (raw)
In-Reply-To: <CAPFanBGbg0qmyUASH_B+uEaOTQni5Qu1tiMKC=OtSEpC9w6NnQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]

Le Fri, 19 Jun 2015, Gabriel Scherer a écrit :
> This change to the placement of attributes that was discussed in
>   http://caml.inria.fr/mantis/view.php?id=6612
>   https://github.com/ocaml/ocaml/pull/152
> 
> It is indeed a mistake that it is not in the Changelog. As a meta-comment
> (not discussing this particular patch), in the future we might need to have
> "a proper Changelog line" as an explicit requirement for all submitted
> patches (I would be tempted to add "a testsuite test exercising the
> affected features"), because it is fairly error-prone to try to track
> changes to add to the changelog after they've been merged.
> 
> The rationale for this change is that the syntax was perceived as an
> improvement by the ppx-users that expressed an opinion on the issue, and
> they asked for this to be released as soon as possible hoping to facilitate
> the transition to the new syntax (few existing users).
> The change was tested against all released OPAM packages, and riak_ppx was
> the only package that broke. It seems that either (1) the code using the
> old syntax had not been released as OPAM packages yet (in retrospect it
> seems reasonable that using OPAM testing as only testing vehicle is rather
> fragile for very recent features; on the other hand, I don't know which
> other tests could be put in place) or (2) said packages did not break in a
> way that was perceptible to the automated tool.

ppx_deriving compiles with 4.02.2, but its tests do not pass. I indeed
have some unreleased code that breaks (it's on a distinct opam repo).
I suspect the tool does not run tests?

The syntax change might be an improvement indeed, but disabling the old behavior
(attaching attributes to record labels) is *breaking* in a way that
makes fixes difficult. For instance, introducing 'nonrec' is breaking,
but in an easy to fix way; the attribute change is hard (you need to
edit code manually to move annotations).

> 
> I think 4.02.2 is a slightly less minor release than is usual: it does have
> some new features that are not simply bugfixes, because they were requested
> by users which were eager to see them released (typically all the
> ppx-related changes). This is a delicate compromise to make, and
> unfortunately there are indeed a couple regressions -- despite a very
> silent rc1-to-release period. The only other one I know of is
> http://caml.inria.fr/mantis/view.php?id=6908 .


-- 
Simon

http://weusepgp.info/
key 49AA62B6, fingerprint 949F EB87 8F06 59C6 D7D3  7D8D 4AC0 1D08 49AA 62B6

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-06-19 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 19:44 Damien Doligez
2015-06-19 11:38 ` Simon Cruanes
2015-06-19 11:59   ` Gabriel Scherer
2015-06-19 12:08     ` Simon Cruanes [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=20150619120805.GV32363@emmental.inria.fr \
    --to=simon.cruanes.2007@m4x.org \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    /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).