-
Notifications
You must be signed in to change notification settings - Fork 98
Dev meeting 16 05 2023
-
5.1.0
support- collaboration with compiler folks in general
- for AST bump: what do we need to discuss for the PPX universe?
-
bisect_ppx
compat with newestppxlib
- OCaml workshop talk on
ppxlib
? - Ppxlib in the OCaml Platform
- Sonja
- Paul-Elliot
Whenever we adapt a parsetree change that's not just a new syntax feature (i.e. parsing change), let's ping the person who introduced the change the compiler. They know the change the best and can help us review our migrations or even help us getting them right. Octachron from the compiler agrees.
Some time in June, the compiler will be released. We need to create the PPX universe. We've agreed that Paul-Elliot will do that this time 🙌
We still have incompat of bisect_ppx
with ppxlib>=0.28.0
due to our traverse class change for error handling:
https://github.com/aantron/bisect_ppx/pull/413
Should we submit a proposal for a talk on ppxlib
to the OCaml workshop this year? Carl is already on board. Possible abstract:
About nine years ago, the OCaml community let go of the "maintenance hell" of source code metaprogramming (Camlp4/5). Since then, meta-programming is mostly done on the parsetree and has incrementally evolved into a solid ecosystem, enriching the OCaml developer experience. Two highlights of that evolvement: introducing parsetree migrations to gain individual cross-compiler compatibility (OMP); and orchestrating those migrations to create an up-to-date ecosystem with clear composition semantics and good performance (ppxlib).
In this talk, we outline the mentioned evolvement and explain the remaining challenges, i.e. creating a good higienic meta-programming culture and offering the best in terms of stability.
Paul-Elliot is on board as well! 🎉 Not for presenting in person in Seattle, but for all the preparation.
Next steps: Sonja shares her first version of the proposal with both.
Remark: Let's use Paul-Elliot's Slipshow to create the presentation! 😎