Open zbaylin opened 10 months ago
Thanks for the report. I reproduced the bug here https://github.com/ocaml/dune/pull/9653
What would be the behavior that you would expect?
Hi @rgrinberg, thanks for helping reproduce the bug.
In my opinion, dune should switch to a bytecode-based driver, or maybe even provide a way of specifying which ppxs to run under bytecode/native mode in the preprocessing
atom.
The ppx I'm running depends on being run under the bytecode runtime, and I'm willing to accept the performance trade off to run it.
Okay, switching to bytecode sounds reasonable enough. Do you want to try implementing this?
Sure, I can look into it. Do you have any pointers as to where I should look for code regarding ppx building/execution?
Expected Behavior
I define a ppx which is expected to compile only as a bytecode library:
I expect this to be applied to my code which depends on
my_ppx
as a preprocessorActual Behavior
The ppx is not applied to the code and extension points remain. This is not the case if I remove the
(modes byte)
.Reproduction
See above
Specifications
dune
(output ofdune --version
): 3.12.1ocaml
(output ofocamlc --version
): 4.14.1