c0deaddict

{ lib, config, pkgs, ... }:

with lib;

let

  veth = "veth-vpn";
  hostIp = "10.0.0.1/24";
  guestIp = "10.0.0.2/24";

denisdefreyne

Person = new Class {{

  firstName: :attr,

  lastName: :attr,

  fullName: function {
    `${this.firstName} ${this.lastName}`
  },

Innf107

{-# LANGUAGE RankNTypes, PatternSynonyms, GADTs, ViewPatterns, LambdaCase, ScopedTypeVariables #-}
module Main where
    
import Data.Map as Map
import Control.Monad (ap, liftM)
import Data.IORef

data ComeFromOp a where
    Line :: Int -> ComeFromOp ()
    LiftIO :: IO () -> ComeFromOp ()

riwsky

#!/bin/bash

# Exit immediately if a command exits with a non-zero status
set -e

jj fix

# Get the list of mutable branches that are reachable from the current branch
# (i.e. that are between us and main).
branches=$(jj branch list -r 'reachable(@,mutable())' --template 'name ++ "\n"')

arianvp

Asynchronous post-build-hook

this hook queues up store paths on a unix domain socket and then spawns a service to actually push the store path to the cache through socket activation

works on MacOS and Linux

davidbarsky

name	rustdoc
description	Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.

Rust Documentation Conventions (RFC 1574)

Apply these rules when writing doc comments (///) on public Rust items.

Summary Sentence