Filmes

or maybe like: diff -r ac91dbef6192 src/version.bash --- a/src/version.bash Mon Mar 08 14:19:28 2010 -0800 +++ b/src/version.bash Tue Mar 09 09:06:40 2010 -0700 @@ -10,10 +10,14 @@ fi # Get numerical revision -VERSION="`hg identify -n`" +VERSION="`hg identify -n | sed 's!.*".*!!'`" +if [[ "$VERSION" == " […]

It's almost entirely due to the regular expression code, which is the (usually) blisteringly fast, written-in-C PCRE for Python but a place-holder, (usually) pretty slow Go-native one in Go, I'm betting at least an order of magnitude slower on average. I hope to see a much more efficient regular expression package for Go before long. Wrapping PCRE […]

I can't find it in the spec either. I suspect it's an oversight. It's an interesting little hole. I'm actually not at all fond of the rule that the type of a shift operation is the type it would have if the left operand appeared alone. It means that, e.g., float(1 […]

This has come up a few times and explanation is that Go's garbage collector is currently slow and the regex library is currently slow. Go isn't stable enough to spend lots of time on optimisations because things will likely change. Premature optimisation etc etc. The optimisations can be done later. […]

I'm writing a simple 'word picker' using golang and python. It basically reads a tweeter message from a csv file, tokenize it and put the word->id into a map called lexicon. It turned out that same logic took 22 seconds for python 2.6 to finish whereas 57 seconds for golang! Wondering are there anything I've done wrong? […]

Russ, Would it make sense for version.bash to try and deal w/ the output from older versions of hg? There is probably a better way, but something like: diff -r 0b7cedc4de63 src/version.bash --- a/src/version.bash Sun Mar 07 12:41:49 2010 +1100 +++ b/src/version.bash Tue Mar 09 06:39:23 2010 -0700 @@ -10,10 +10,10 @@ […]

Absolutely. What I meant to say was that Go will need a language standard before it leaves the sandbox stage, and not that it needs one today. Sorry if I didn't make that clear. […]

I'm trying to understand the type system for shift expressions. Take the following example: package main func f(s1 uint, s2 uint) bool { return ((1 […]

I didn't start out trying to complain, merely to observe that Go really needs generics (not in the absolute you-can't-do-anything-without- them sense, just in the their-absence-will-seriously-h inder-adoption sense). Then a few tried to convince me how simple and easy everything is without generics, implying that Go can do without them. I disagreed […]

this has been discussed before, in this thread: [link] your code looks pretty good though. i've made a few comments on your blog page. […]