From fe53a39c6596970c338bfcb935a578a1b2f7f2e7 Mon Sep 17 00:00:00 2001 From: Lukasz Stafiniak Date: Fri, 15 Dec 2023 13:27:49 +0100 Subject: [PATCH] Remove outdated comment --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 5d2d439..5d44a85 100644 --- a/README.md +++ b/README.md @@ -218,8 +218,6 @@ The `%debug_this` variants are intended only for `let`-bindings: `let%debug_this To properly trace in concurrent settings, ensure that different threads use different log channels. For example, you can bind `Debug_runtime` locally: `let module Debug_runtime = Minidebug_runtime.Flushing(struct let debug_ch = thread_specific_ch let time_tagged = true end) in ...` In particular, when performing `dune runtest` in the `ppx_minidebug` directory, the `test_debug_n` and the `test_debug_n_expected` pairs of programs will interfere with each other, unless you adjust the log file names in them. -`Minidebug_runtime.Debug_ch` appends to log files, so you need to delete them as appropriate for your convenience. - The `PrintBox` logs are the prettiest, I could not get the `Pp_format`-functor-based output look the way I wanted. The `Flushing` logs enable [Log Inspector (sub-millisecond)](https://marketplace.visualstudio.com/items?itemName=lukstafi.loginspector-submillisecond) flame graphs. One should be able to get other logging styles to work with `Log Inspector` by configuring its regexp patterns. `ppx_minidebug` can be installed using `opam`. `ppx_minidebug.runtime` depends on `printbox`, `ptime`, `sexplib0`.