Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

constrain ppx_deriving 4.2.1 to ocaml > 4.03.0 #10807

Merged
merged 1 commit into from
Nov 22, 2017

Conversation

yomimono
Copy link
Member

ppx_deriving 4.2.1 is great to have released, but it does not contain a fix for ocaml-ppx/ppx_deriving#147 (duplicated code when using it with 4.03). ppx_deriving 4.2 is listed as available for OCaml > 4.03.0 because of this issue; propagate that to 4.2.1.

@yomimono yomimono changed the title make ppx_deriving 4.2.1 available for > 4.03.0 constrain ppx_deriving 4.2.1 to ocaml > 4.03.0 Nov 22, 2017
@camelus
Copy link
Contributor

camelus commented Nov 22, 2017

✅ All lint checks passed 25d8a25
  • These packages passed lint tests: ppx_deriving.4.2.1

✅ Installability check (7787 → 7787)

@yomimono
Copy link
Member Author

/cc @gasche ; I may have misunderstood something about what's included in 4.2.1 or the actual source of the code duplication, but it does appear to be happening with 4.2.1 still (see this build log for cohttp and ppx_deriving 4.2.1 on 4.03).

@samoht samoht mentioned this pull request Nov 22, 2017
@gasche
Copy link
Member

gasche commented Nov 22, 2017

Thanks, indeed I don't think 4.2.1 fixes this issue (I don't understand the issue but the discussion suggests that the problem lies with ppx_type_conv), so I believe that your fix is the right thing to do. Thanks!

(This also supports the idea of indeed having a 4.1 maintenance release as I believe the non-driverized 4.1 does not suffer from the issue.)

@gasche gasche merged commit 35e6cc4 into ocaml:master Nov 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants