Corentin Leruth tatchi

name	description
Logging Best Practices	Use before implementing logs in a medium to large scale production system.

This skill is adpated from "Logging sucks. And here's how to make it better. by Boris Tane.

When helping with logging, observability, or debugging strategies, follow these principles:

Core Philosophy

A pattern for using GADTs to subset cases

Consider the following straightforward mutable queue implementation using two stacks:

type 'a adt_queue = {
  mutable head : 'a head;
  mutable tail : 'a tail;
}

a thread where we can discuss some crazy routing ideas a bit out in the open branching out from the previous discussion on filesystem routes over at: https://discord.com/channels/815937377888632913/1014946079965454366

so, first of all, it seems there is a close alignment between how vite-plugin-ssr and router5 handles routing:

vps: (view === 'overview') @ https://vite-plugin-ssr.com/layouts#nested-layouts
router5 (route === 'dashboard') @ https://youtu.be/hblXdstrAg0?t=197 maybe with the small exception that router5 has the explicit perspective of routes as app state whereas I didn't get the impression from vps that it's viewed as such (even though it technically is still state).

I recommend watching this router5 talk from 2:45 - 7:50 https://youtu.be/hblXdstrAg0?t=165 since it's really key to how I think about view / state separation, and I think of routing as a state separate from the view. (After all, and especially in a client-rendered app, what page it is showing is certainly a major part

	import { randomString } from "./benchUtil.js";
	import { metabench } from "./metabench.js";

	export function lazyWithInternalProp<T>(getter: () => T) {
	return {
	__value: undefined as T,
	get value() {
	if (this.__value) return this.__value;
	const value = getter();
	this.__value = value;

	open ContainersLabels

	let read_file name = CCIO.(with_in name read_lines_l)

	let rec try_parse parsers line =
	match parsers with
	\| [] -> failwith ("could not parse: " ^ line)
	\| parse :: parsers -> (
	match parse line with
	\| None -> try_parse parsers line

	import type { Server } from "node:http";

	export type Handler = (request: Request) => Response \| Promise<Response>;

	export type CreateServerOptions = {
	onError?: (error: unknown) => void;
	};

	export declare function createServer(
	handler: Handler,

	import Breakpoints from './Breakpoints';
	import { css, cx } from '@emotion/css';
	import { HTMLAttributes, forwardRef } from 'react';

	export type StackProps = {
	adaptive?: true;
	alignCenter?: true;
	center?: true;
	children?: React.ReactNode;
	className?: string;

	import { getHighlighter as shikiGetHighlighter } from "shiki";
	import { cache } from "react";

	interface ShikiProps {
	code: string;
	lang: string;
	theme: string;
	}

	export async function Shiki({ code, lang, theme }: ShikiProps) {

	import * as Context from "@effect/data/Context";
	import { pipe } from "@effect/data/Function";
	import * as Effect from "@effect/io/Effect";
	import * as Exit from "@effect/io/Exit";
	import * as Layer from "@effect/io/Layer";
	import { uniqueId } from "lodash-es";

	import {
	Prisma,
	PrismaClient,

	// TODO: make `pages` optional and measure the div when unspecified, this will
	// allow more normal document flow and make it easier to do both mobile and
	// desktop.
	import {
	createContext,
	useCallback,
	useContext,
	useEffect,
	useMemo,
	useRef,