`PrintBox.no_debug_if` functionality

When module Debug_runtime = Minidebug_runtime.PrintBox(...), Debug_runtime.no_debug_if allows to hide irrelevant or distracting logs (e.g. when there is no change). An entire subtree of the logs is hidden.

0.3.3 Optional time tags

Optional time tags make testing easier, and logs look nicer without time stamps.

0.3.2

CHANGES:

Fixed

• Third time the charm! Missing version bounds on ocaml and ppxlib to make CI happy.
• BSD-compatible sed arguments to make CI happy.

0.3.1

CHANGES:

Fixed

• A small tweak to have dune-release work.

Bug fix and build cleanup release

• Breaking change: renamed Minidebug_runtime.Format to Minidebug_runtime.PP_format.
• Non-optionally depending on sexplib0 and ppx_sexp_conv, as optional dependency was making it hard to test. Also the minidebug_runtime source files duplication was ugly.
• Trying to minimize dependencies: removed the unused direct dependency on base, but ppx_sexp_conv depends on it. Removed the dependency on stdio.
• Added a building-related comment to the documentation.
• Major bug fix: missing processing of the top expression in a function body.

Pull in the `minidebug_runtime` package as `ppx_minidebug.runtime`

Fixes #2 and makes ppx_minidebug rewriter dependent on the minidebug_runtime library (which it does not strictly need to be, but for practical purposes is).

Handle labeled function arguments

Fixes handling of labeled function arguments, and expands suggestions regarding VOCaml.

First wide release of `ppx_minidebug` and `minidebug_runtime`

In this release of ppx_minidebug:

• Which is a syntax extension to instrument type-annotated bindings and functions with logging.
• The extension supports 3 value conversion mechanisms: pp and show from deriving.show, and sexp from ppx_sexp_conv.
• The minidebug_runtime package provides 3 logging backends: Format based purely on formatters, Flushing that converts to strings first and flushes output after every entry, and PrintBox that pretty-prints as trees using the printbox package.
• I reference a VS Code extension that builds flame graphs for the Flushing logger out-of-the-box.
• I provide documentation and publish the API docs on github.io.
• I provide tests, including testing the writing-to-files functionality. (I use sed for sanitizing...)