-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[new release] ppxlib.0.33.0 #26251
[new release] ppxlib.0.33.0 #26251
Conversation
1519b6c
to
b50d042
Compare
Thanks @mbarbin for finding out about the malformed opam file. I kind of created the PR and left it there because the CI takes a while to run and didn't check that it actually started running. |
I went through the 5.2 revdeps failures and couldn't find anything that seemed ppxlib related. I'll wait for the 4.14 revdeps failures before undrafting anyway, just in case some packages aren't compatible with 5.2 yet. CC @mseri or any other opam-repo maintainers, do you spot anything unusual in the revdeps failures here? |
It seems there's quite a few revdeps build that weren't over when I reviewed the first time, I'll take some time to look at those and the non overlapping 4.14 ones. |
I don't see regressions, but most jobs are failing with solver timeouts, so who knows... :( I have already opened an issue on the ocaml infrastructure repository about the timeouts, they are not limited to this PR. So we should not consider this a blocker for this PR. |
I think I went through most, if not all meaningful build failures on 5.2 and couldn't find errors related to this release so I will proceed with undrafting. I have a feeling that the number of false positives on |
Ah, just missed your message, thanks for your help on this! |
Here is the issue: ocaml/infrastructure#147 |
- Fix a bug where `Code_path.main_module_name` would not properly remove extensions from the filename and therefore return an invalid module name. (ocaml-ppx/ppxlib#512, @NathanReb) - Add `-unused-type-warnings` flag to the driver to allow users to disable only the generation of warning 34 silencing structure items when using `[@@deriving ...]` on type declarations. (ocaml-ppx/ppxlib#511, @mbarbin, @NathanReb) - Make `-unused-code-warnings` flag to the driver also controls the generation of warning 34 silencing structure items when using `[@@deriving ...]` on type declarations. (ocaml-ppx/ppxlib#510, @mbarbin, @NathanReb) - Driver: Add `-unused-code-warnings=force` command-line flag argument. (ocaml-ppx/ppxlib#490, @mbarbin) - new functions `Ast_builder.{e,p}list_tail` that take an extra tail expression/pattern argument parameter compared to `Ast_builder.{e,p}list`, so they can build ASTs like `a :: b :: c` instead of only `[ a; b ]`. (ocaml-ppx/ppxlib#498, ocaml-ppx/ppxlib#502, @v-gb, @NathanReb) - Fix `Longident.parse` so it also handles indexing operators such as `.!()`, `.%(;..)<-`, or `Vec.(.%())` (ocaml-ppx/ppxlib#494, @Octachron) - Add a `special_function'` variant which directly takes a `Longident.t` argument to avoid the issue that `Longident.t` cover distinct syntaxic classes which cannot be easily parsed by a common parser (ocaml-ppx/ppxlib#496, @Octachron). - Keep location ranges consistent when migrating `Pexp_function` nodes from 5.2+ to older versions (ocaml-ppx/ppxlib#504, @jchavarri) - Fix `-locations-check` behaviour so it is no longer required to pass `-check` as well to enable location checks. (ocaml-ppx/ppxlib#506, @NathanReb) Signed-off-by: Nathan Rebours <[email protected]>
b50d042
to
e02e528
Compare
This should be good to go, let me know if anything's blocking! |
Hi, @NathanReb 👋 :) Do you think this test failure on
|
No, that is quite an old failure. I think this is good to merge
|
Release of ppxlib.0.33.0.
Changes
Fix a bug where
Code_path.main_module_name
would not properly remove extensions from the filename and therefore return an invalid module name.(Fix extension removal bug in
Code_path.main_module_name
ocaml-ppx/ppxlib#512, @NathanReb)Add
-unused-type-warnings
flag to the driver to allow users to disable only the generation of warning 34 silencing structure items when using[@@deriving ...]
on type declarations.(Add an -unused-type-warnings flag to the driver (bis) ocaml-ppx/ppxlib#511, @mbarbin, @NathanReb)
Make
-unused-code-warnings
flag to the driver also controls the generation of warning 34 silencing structure items when using[@@deriving ...]
on type declarations.(Make
-unused-code-warnings
also controls warning 34 suppression items ocaml-ppx/ppxlib#510, @mbarbin, @NathanReb)Driver: Add
-unused-code-warnings=force
command-line flag argument.(Add driver flag to force opting in to unused code warnings in derived code ocaml-ppx/ppxlib#490, @mbarbin)
new functions
Ast_builder.{e,p}list_tail
that take an extra tail expression/pattern argument parameter compared toAst_builder.{e,p}list
, so they can build ASTs likea :: b :: c
instead of only[ a; b ]
.(make Ast_builder.{e,p}list able to build lists such as
a :: b :: c
ocaml-ppx/ppxlib#498, Rename and modify e/plist_v2 to e/plist_tail ocaml-ppx/ppxlib#502, @v-gb, @NathanReb)Fix
Longident.parse
so it also handles indexing operators such as.!()
,.%(;..)<-
, orVec.(.%())
(Context_free.special_function: fix the parsing of indexing operators ocaml-ppx/ppxlib#494, @Octachron)
Add a
special_function'
variant which directly takes aLongident.t
argument to avoid the issue thatLongident.t
cover distinct syntaxic classes which cannot be easily parsed by a common parser(Context_free: add a special_function' variant ocaml-ppx/ppxlib#496, @Octachron).
Keep location ranges consistent when migrating
Pexp_function
nodes from 5.2+ to older versions(Fix issue 503 ocaml-ppx/ppxlib#504, @jchavarri)
Fix
-locations-check
behaviour so it is no longer required to pass-check
as well to enable location checks.(Fix -locations-check behaviour ocaml-ppx/ppxlib#506, @NathanReb)