fxg42

defmodule Optional do
  def unit(nil), do: {:err, nil}
  def unit(value), do: {:ok, value}

  def lift(func) do
    fn input -> unit(func.(input)) end
  end

  def bind({:ok, optional}, functor), do: functor.(optional)
  def bind(err, _), do: err

dblock

class OauthController < ApplicationController

  class ApiOAuthError < StandardError

    attr_accessor :code, :description, :uri, :state
    
    def initialize(code, description, uri = nil, state = nil)
      @code = code
      @description = description
      @uri = uri

jmont

// Swift Monads -- Maybe
// Juan C. Montemayor (@norsemelon)

// This operator can be used to chain Optional types like so:
// optionalVal >>= f1 >>= f2
// where f1 and f2 have type `Any -> Any?`
//
// If a value is ever nil, the chain short-circuits and will result in nil.
// This is a much neater way to do this than using the if syntax specified in
// the Swift iBook.

swlaschin

(*
Demonstrates DTO validation for a news feed domain
*)

// "result.fsx" comes from https://github.com/swlaschin/DmmfWorkshop/blob/master/src/E-ModelingErrors/Result.fsx
#load "result.fsx"

module Domain =
    type DocumentId = DocumentId of int
    type EmailAddress = EmailAddress of string

timruffles

In many production systems you'll want to have one module capable of talking to many potential implementations of a collaborator module (e.g a in memory cache, a redis-based cache etc). While testing it's useful to control which module the module under test is talking to.

Here are the approaches I can see. The two points that seem to divide the approaches are their tool-ability (dialyzer) and their ability to handle stateful implementations (which need a pid).

Passing modules

Modules are first class, so you can pass them in. Used in EEx, where passed module must implement a behaviour.

swlaschin

(*
ParserLibrary_v1.fsx

Version 1 of the code for a parser library.

Related blog post: http://fsharpforfunandprofit.com/posts/understanding-parser-combinators/

*)

open System

mattbaggott

#
# PREDICTING LONG TERM CUSTOMER VALUE WITH BTYD PACKAGE
# Pareto/NBD (negative binomial distribution) modeling of 
# repeat-buying behavior in a noncontractual setting
#
# Matthew Baggott, matt@baggott.net
#
# Accompanying slides at:
# http://www.slideshare.net/mattbagg/baggott-predict-customerinrpart1#
#

chriseidhof

import Foundation

class Box<T> {
    let unbox: T
    init(_ value: T) { self.unbox = value }
}

struct Notification<A> {
    let name: String
}

he9lin

Setup Rails application production environment on Ubuntu

Add deploy user

ssh root@YOURDOMAIN
adduser deploy
visudo # Add deploy ALL=(ALL) ALL

Install necessary libraries

ryanb

#!/usr/bin/env bash
apt-get -y update
apt-get -y install build-essential zlib1g-dev libssl-dev libreadline5-dev libyaml-dev
cd /tmp
wget ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p125.tar.gz
tar -xvzf ruby-1.9.3-p125.tar.gz
cd ruby-1.9.3-p125/
./configure --prefix=/usr/local
make
make install