Corentin De Souza

Includes https://github.com/LexiFi/dead_code_analyzer/pull/35, and https://github.com/LexiFi/dead_code_analyzer/pull/41. To be reviewed after [1.0.1](https://github.com/LexiFi/dead_code_analyzer/pull/35). Other than updating the OCaml version to 5.3 and fixing the compilation mistakes, this PR includes 2 import changes : -...

Given a simple project architecture : ``` . ├── bin │   ├── dune │   └── main.ml ├── dune-project ├── lib │   ├── bar.ml │   ├── bar.mli │   ├── dune │  ...

Add tests using ppx and add support for preprocessed files. This contributes to https://github.com/LexiFi/dead_code_analyzer/issues/40 for OCaml 5.2. It applies the suggested solution. It works well (based on the tests results)...

Ready for release : `opam install .` works as expected. Upon approval of this PR, I'll publish the package on opam. This release includes: - https://github.com/LexiFi/dead_code_analyzer/pull/26 - https://github.com/LexiFi/dead_code_analyzer/pull/27 - https://github.com/LexiFi/dead_code_analyzer/pull/29...

The current compatible OCaml version is 5.2. The latest OCaml release is 5.4.0. There is interest in having an OCaml 5.3 compatible version (https://github.com/LexiFi/dead_code_analyzer/pull/17#issuecomment-3199461320, and https://github.com/LexiFi/dead_code_analyzer/pull/31#issuecomment-3603188491). This would also provide...

# Context Currently, the output of the `dead_code_analyzer` is sorted lexicographic order in each report section, with an empty line in between directory changes. Below is a sample pseudo-output, copied...