Add support for Eio library in dependency analysis; enhance caching mechanism with skip options and improve benchmark testing. Update README with new test instructions and add benchmark executable.

Author: mununki

README.md

@@ -50,23 +50,46 @@ You can run tests using the following methods:
 # Run all tests
 dune runtest
 
-# Run tests in a specific directory
-dune runtest test/
+# Run specific tests:
+dune exec test/test_cmt_values.exe   # Directly execute the test
+dune exec test/test_cmt_imports.exe  # Directly execute the test
 
-# Run specific tests
-dune runtest test/test_cmt_imports.exe
-dune runtest test/test_cmt_values.exe
-
-# Run tests directly
-dune exec test/test_cmt_imports.exe
+# Run benchmark
+dune build @bench                    # Build and run the benchmark
+dune exec test/benchmark.exe         # Directly execute the benchmark
 ```
 
 Test code is located in the `test/` directory and includes the following tests:
 
 - `test_cmt_imports.ml`: Tests the import information from cmt files.
 - `test_cmt_values.ml`: Tests the value dependency information from cmt files.
+- `test_rescriptdep.ml`: Basic smoke test for the rescriptdep functionality.
+- `benchmark.ml`: Performance benchmark for the parser.
+
+#### Running the Benchmark
+
+The benchmark is designed to be run separately from the regular tests and requires a ReScript project with compiled .cmt files to analyze:
+
+```bash
+# Run the benchmark with a specific ReScript project
+RESCRIPTDEP_BENCHMARK_PATH=/path/to/rescript/project/lib/bs/src dune exec test/benchmark.exe
+
+# Example with environment variables for detailed output
+RESCRIPTDEP_BENCHMARK=1 RESCRIPTDEP_VERBOSE=1 RESCRIPTDEP_BENCHMARK_PATH=/path/to/project/lib/bs/src dune exec test/benchmark.exe
+```
+
+When running as part of `dune runtest`, the benchmark will be skipped automatically.
+
+#### Test Fixtures
+
+Fixture files used by tests are located in the `test/fixtures/` directory. These files include:
+
+- `app.cmt`: Example application module.
+- `math.cmt`: Example math utility module.
+- `logger.cmt`: Example logging module.
+- `utils.cmt`: Example utilities module.
 
-When modifying test code, check the configuration in the `test/dune` file. Fixture files used by tests are located in the `test/fixtures/` directory.
+Tests automatically locate these fixture files, so they should work correctly regardless of your current working directory.
 
 ## License
 

bin/main.ml

@@ -100,8 +100,11 @@ let main () =
       if !skip_cache then (
         if !verbose then Printf.eprintf "Skipping cache usage\n";
         Rescriptdep.Parser.clear_cache ();
-        Rescriptdep.Parser.parse_files_or_dirs ~verbose:!verbose !input_files)
-      else Rescriptdep.Parser.parse_files_or_dirs ~verbose:!verbose !input_files
+        Rescriptdep.Parser.parse_files_or_dirs ~verbose:!verbose
+          ~skip_cache:true !input_files)
+      else
+        Rescriptdep.Parser.parse_files_or_dirs ~verbose:!verbose
+          ~skip_cache:false !input_files
     in
 
     time_checkpoint "Parsing completed";

dune-project

@@ -25,6 +25,8 @@
   (ocaml
    (= 5.3.0))
   dune
+  eio
+  eio_main
   (odoc :with-doc))
  (tags
   (topics "dependency analysis" "ReScript" "OCaml")))

lib/dune

@@ -4,4 +4,4 @@
   (:standard -w -27-32-33-34-37-39-50-52))
  (public_name rescriptdep)
  (modules parse_utils parser formatter dependency_graph)
- (libraries str unix vendor))
+ (libraries str unix vendor eio eio_main))