jtacoma

// Given a prototype-like object, create a class based on that object's
// properties.
function buildClass(spec) {
  // Throw an exception of the argument is inappropriate:
  if (typeof(spec) != 'object' || spec === null)
    throw 'expected an object.';
  var empty = true;
  for (var name in spec) { empty = false; break; }
  if (empty)
    throw 'expected a non-empty object.';

jtacoma

<dl>
  <dt>selector</dt>
    <dd>dl</dd>
  <dt>apply</dt>
    <dd>
      <ul>
        <li>
          <dl>
            <dt>selector</dt>
              <dd>&gt; dt</dd>

jtacoma

$ cat <<EOF > sample.txt
> title: Sample!
>
> = {{ title }} =
> EOF
$ yaml-assemble sample.txt | mustache | creole2html
<h1>Sample!</h1>

jtacoma

var $ = require('jquery');

function chunkify(rawHtml, chunks) {
  var woven = $(rawHtml).find("code[title!='']");
  for (var i = 0; i < woven.length; ++i) {
    var element = $(woven[i]);
    var content = element.text();
    var name = element.attr("title");
    if (chunks[name])
      chunks[name] = chunks[name].concat(content);

jtacoma

// This package demonstrates a technique for (very nearly) adding methods
// to an interface.  The code works and runs as is.
package main

import "fmt"

// A simple custom type
type Cell int

// CellSetMinimal is a (very) minimal interface to be easily implemented

jtacoma

// Though it's not necessary, you might want to run this with environment
// variable GOMAXPROCS set to the number of CPUs on your machine.
//
// For example, at a bash prompt:
//
//  $ GOMAXPROCS=4 go run echo.go
//
package main

import (

jtacoma

.cache
getsockopt-*.go
setsockopt-*.go
socket*.go

jtacoma

Changing the Public API

When I started looking for ways to help on the "github.com/alecthomas/gozmq" package a few months ago, a recurring topic in discussions was that an earlier decision to provide a hidden struct type through a public interface type had become restrictive. We couldn't just drop the interface and make the struct public because that would be backwards-incompatible. Or could we?

No

This had to be the first considered option, and was the standing decision at the time. If we could continue providing what the package aims to provide without breaking backwards compatibility, then by all means, we should not break it.

Unfortunately this meant we couldn't provide all that we aimed to provide. Or could we?

jtacoma

package main

import (
	"log"
	"time"

	zmq "github.com/alecthomas/gozmq"
)

func main() {

jtacoma

// Package bar provides thneeds (things everyone needs).
//
// Those switching from "example.com/pkg/foo" to bar will have to run the
// following commands (which are intended to be idempotent).
//
//     go fmt -r 'a.ChopTruffulaTree(b) -> a.ChopTruffulaTrees(b, b, b, b, b)'
//
// Of course, if you're using sufficiently smart tools, your code may already
// be updated.
//