| // support for arbitrary number of channels of type string | |
| func nonDeterministicChanMultiPlexer(channels ...chan string) <-chan string { | |
| outChan := make(chan string) | |
| for _, c := range channels { | |
| go func(cc chan string) { | |
| for { | |
| outChan <- <-cc | |
| } | |
| }(c) |
go build: compiles the packages named by the import paths,
along with their dependencies, the binary does not end up in $GOPATH/bin it gets created in the dirs
go build [-o output] [build flags] [packages]
If the [packages] are a list of .go files, build treats them as a list of source files specifying a single package.
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso