removed (ocaml-migrate-parsetree (>= 2.2.0)) from dune-project,
bootstrapped,
and then locally pinned the directory to let opam compile and install the library.
Compared to libclang-11, "const" are not seen by the parser in LValueReferences: do you know if something changed between those version that would explain this behaviour?
Example: in the following code, the two "const" are missed.
class AFM_API tfm_acquisition_PE_specification : public acquisition_specification
{
public:
struct implementation;
tfm_acquisition_PE_specification(const tfm_acquisition_PE_specification& other);
tfm_acquisition_PE_specification& operator=(const tfm_acquisition_PE_specification& other);
~tfm_acquisition_PE_specification();
Hello.
I managed to install clangml with libclang-16 on a bookworm debian (WSL) with ocaml 5.1.1:
(ocaml-migrate-parsetree (>= 2.2.0))
fromdune-project
,Compared to libclang-11, "const" are not seen by the parser in LValueReferences: do you know if something changed between those version that would explain this behaviour?
Example: in the following code, the two "const" are missed.
If i dump the AST, I obtain something like that:
while I have
const = true
with libclang-11.I hope my question is understandable.