Runtime Logger Selection in OCaml Using First-Class Modules
Package an OCaml module as a value and choose a logging backend at runtime without losing compile-time type checks.
Loading…
ReadMeFeed / Community knowledge
#dune
Real questions. Useful conversations. Find the people who know your stack.
ocamlEnforcing Reproducible OCaml Builds with Dune Explicit Dependencies
Learn how to use Dune's explicit module and library stanzas to eliminate implicit dependencies and ensure reproducible, sandboxed OCaml builds.
Sealing OCaml Libraries and Sharing Test Code with Dune Without Bloating Your Binary
A practical guide to using Dune's wrapped libraries, .mli sealing, and inline tests to share code between executables and test suites while keeping production binaries lean.
Cutting Boilerplate with ppx_deriving: Where OCaml's Code Generation Pays Off
ppx_deriving generates compare, show, and equality functions from one annotation, keeping them correct as types evolve — but generated code has real costs in error readability and build complexity worth understanding first.
Resolving Unbound Module and Unbound Value Errors in OCaml with Dune
A diagnostic guide to fixing 'Unbound module' and 'Unbound value' errors in OCaml. Learn how to audit Dune configurations, resolve naming conflicts, and handle circular dependencies.
Dune Flag Propagation and OCaml -w Syntax: Overlapping Range Precedence
When configuring OCaml compiler warnings through the -w flag, the interaction between Dune's build defaults and the compiler's own warning syntax creates ambiguity in complex projects. The -w flag accepts comma-separated warning numbers or ranges with + , - , or = prefixes, but the precise precedence rules remain unclear when a warning number falls inside bo
OCaml compiler .cmt/.cmi and Dune cache invalidation on compiler flag changes
OCaml compiler emits .cmi and .cmt files that capture type information for later reuse. Dune orchestrates builds and reuses compiled .cmo and metadata artifacts based on source file timestamps and content. The integration boundary is unclear when compiler options such as -I include paths, -ccopt, or -g change. Dune currently does not treat flag changes as de