Pull in typewriter package

[clipperhouse]

Pull in typewriter package

[freeeve]

Seems reasonable. I was thinking it seemed like there was an extra package somewhere in the new layout.

[clipperhouse]

It appears this is a no-go – a gen package with a main() (that is, a package intended to be installed as a binary) cannot also be used as an import.

At least, not in my experiments. Is the above true?

[maddyblue]

You can import a package named main with a main() func, but you must name the import:

$GOPATH/src/a/main.go:

package main

import b "b" // just `import "b"` won't work here - try it

func main() {
    println("a")
    b.Hi()
}

$GOPATH/src/b/main.go:

package main

func main() {
    println("b")
}

func Hi() {
    println("hi")
}

$ go run $GOPATH/src/a/main.go
a
hi

[freeeve]

You could also do something like go get github.com/clipperhouse/gen/gen for the binary w/ main--you'd have to put it in a subfolder though. This is also necessary for the gopkg.in router--had to do it for https://github.com/wfreeman/pj

[clipperhouse]

@mjibson @wfreeman Thanks, I suspected the workarounds would look like that. I think both are a bit error-prone for clients of the package, though the subfolder offends me slightly less.

I think a subfolder for the binary is def a no-go from a design perspective. A simpler URL for installers wins, since they are the majority of users.

So then the library is the thing. Do we ask people to import clipperhouse/typewriter or clipperhouse/gen/gen?

[clipperhouse]

The typewriter package is still separate, but part of the main gen repo. Good enough for now.