[go-nuts] Re: Idiomatic deletion from a slice?

Yes, I looked at that, it explains how to delete from a slice - isn't that
what I'm doing in my code<https://github.com/mindplay-dk/riot.go/blob/master/observable.go#L75>
?

So I just set up a brand new Go 1.2.1 on my new computer tonight, and
checked out my code and ran it - and now, what should be two calls, and was
3 calls on my other system, generates 5 calls on this system!

Could somebody run the test on their setup and compare the output?

=== RUN TestObservable
--- FAIL: TestObservable (0.00 seconds)
observable_test.go:23: LoadEvent handler #1: LoadEvent#1
observable_test.go:30: LoadEvent handler #2: LoadEvent#1
observable_test.go:37: SaveEvent once-handler #1: SaveEvent#1
observable_test.go:44: SaveEvent handler: SaveEvent#1
observable_test.go:44: SaveEvent handler: SaveEvent#2
observable_test.go:55: SaveEvent once-handler #2: SaveEvent#3
observable_test.go:44: SaveEvent handler: SaveEvent#3
observable_test.go:30: LoadEvent handler #2: LoadEvent#2
observable_test.go:30: LoadEvent handler #2: LoadEvent#2
observable_test.go:30: LoadEvent handler #2: LoadEvent#3
observable_test.go:30: LoadEvent handler #2: LoadEvent#3
observable_test.go:76: expected 2 calls to LoadEvent handler #2, got 5
FAIL
exit status 1
FAIL github.com/mindplay-dk/riot 0.512s

Meanwhile, I am none the wiser, and slice deletion, as explained on the
wiki (and here) doesn't make a lick of sense to me.

It's making me feel pretty dumb. This must be the first and least idiomatic
thing I've seen in Go so far - an operation this basic should not make you
feel dumb, and should not require code that is, more or less, void of any
semantics.

I love the simplicity of Go, but this doesn't seem simple at all - it seems
unnecessarily complicated, and I'm more than a a little taken aback by
this... :-/

Any better alternatives - or any hope of this improving in the future?

Thanks,
   Rasmus