kassane

A simple overview of Zig's std.log for Zig v0.12.0 or higher

Logging functionality that supports:

• If a log message should be printed is determined at comptime, meaning zero overhead for unprinted messages (so just leave the code peppered with debug logs, but when it makes sense scope them; so downstream users can filter them out)
• Scoped log messages
• Different log levels per scope
• Overrideable log output (write to file, database, etc.)
• All the standard std.fmt formatting magic

Basic Usage:

henrik

1. Your class can be no longer than 100 lines of code.
2. Your methods can be no longer than five lines of code.
3. You can pass no more than four parameters and you can’t just make it one big hash.
4. When a call comes into your Rails controller, you can only instantiate one object to do whatever it is that needs to be done. And your view can only know about one instance variable.

You can break these rules if you can talk your pair into agreeing with you.

bobby

(ns datomic-helpers
  (:require [datomic.api     :as d]))

;;; Expose Datomic vars here, for convenience

;;; Ring middleware

(defn wrap-datomic
  "A Ring middleware that provides a request-consistent database connection and
  value for the life of a request."