-
Notifications
You must be signed in to change notification settings - Fork 99
dev meeting 20220223
Present at the meeting:
- Paul-Elliot Anglès d'Auriac (@panglesd)
- Aya Charaf (@ayc9)
- Sonja Heinze (@pitag-ha)
- Sonja finishes creating the ppx-universe
- Paul-Elliot improves the way ppxlib itself reports errors
- Paul-Elliot works on the documentation/manual
- Aya wraps up the
[@@make]
deriver and prepares a presentation
None of us three has had very much time to work on ppxlib
these past two weeks.
Paul-Elliot has started looking into turning the located exceptions raised by ppxlib
itself into embedded error extension nodes whenever possible. He'll keep on working on that. He has also worked a bit on the documentation by having a look at the question if it would be feasible to "odocify" the compiler Parsetree
module: currently, that module contains very useful non-documentation comments that could be turned into documentation comments. The answer to the question is: with one small improvement of odoc which will be merged soon, it is feasible. So he'll open an issue at the compiler to see if the compiler devs would be happy with him implementing that change.
Aya has kept on working on the make
deriver, which isn't completed yet. She'll keep on working on it and hopefully open a PR soon. She'll also prepare a presentation about her work done so far.
Sonja has worked a bit on the ppx-universe. She first ran into a bug with opam-monorepo
. Pinning to an older opam-monorepo
version and adjusting some things manually, she's now able to create the current ppx-universe. However, when trying to compile it, ocaml throws a "version [unspecified] not understood" exception. She'll find out what's going on and will hopefully soon be able to get a good picture of how much the 4.14 AST bump impacts the PPX ecosystem. Depending on that, she'll decide if to add an extra stable layer to Ast_builder
and to Ast_pattern
for this bump or not.
Sonja has also written up what objectives and priorities ppxlib
currently has, trying to reflect the community's needs and wishes. Of course, number one and two are the 4.14/5.00 AST bump and improving the docs, but there are also other things that could/should be done. We've discussed those objectives during the meeting and will make them public soon.