Closed Niols closed 3 years ago
The other idea that I had in the meantime was to write a tiny custom PPX just for the compilation of this CST file. This would avoid a textual manipulation of the type definitions and make this part of the code more robust. I can give it a try and open yet another PR. We'd have to choose between the approaches:
What do you think would be preferable? I would say 2. is better than 1., but maybe 3. is better than both and I should just do that?
@Niols Can you please rebase your branch on top of master to check that the new CI is green?
Gitlab offers a rebase
button but Github, unfortunately, does not.
Just rebased master into this PR. I had already checked the CI so it should be all green unless I did something very wrong!
All green!
Same as #126 except the splitter has been rewritten in OCaml. This does not make the compilation faster or clearer. It does allow for a better documentation of the process (in particular, the regexp can be split and documented in tiny bits). More importantly, it fixes the compilation on Windows, which we will see once we integrate the new CI (see #127).
We have to choose between this PR, #126 or none of the two if we don't validate the concept. @yurug, WDYT?