11h
awarded Enlightened
12h
awarded Nice Answer
14h
comment Subscriber with lazy evaluation
@ril: 'Lazy evaluation' is a well defined term, no problem about it. 'Subscribe' is not a well defined term generally, and especially in the context of the Go specs - nothing like that is ever mentioned there. It's not that I cannot imagine what one can mean by 'subscribe' in Go. It's about the situation where I can imagine several different concepts available in Go which might deserve that name. One of the first ("subscribing") possibilities which come to my mind is receiving from a channel. Seemingly that's not what you are talking about.
21h
comment Subscriber with lazy evaluation
I owe a beer to the first person who can explain to me what is this question about. - Undefined terms "subscribe", "source attributes". - Undefined notation "/foo", "[foo]./bar --> whatever".
1d
answered How to identify Go program CPU usage hot spots?
1d
answered Is there an easy way to iterate over a map in order?
Jun
14
answered Strange behaviour of goroutine and channel communication
Jun
13
comment Go correct behaviour, or compiler bug?
@HowardGuo: Please see the updated answer. I'll check if it is a known issue and report it if not.
Jun
13
answered Go correct behaviour, or compiler bug?
Jun
13
comment Go embedded databases
+1 for adding kv ;-)
Jun
13
answered What is the most effective way to lock down external dependency "versions" in Golang?
Jun
12
comment Replace a regular expression submatch using a function
@dystroy: Please see the updated answer.
Jun
12
revised Replace a regular expression submatch using a function
added 815 characters in body
Jun
12
answered Replace a regular expression submatch using a function
Jun
11
comment Is Go developed enough to use it to make the core of an operating system?
@user2450516: With the reservation of "some assembly required/unavoidable", yes.
Jun
10
answered Golang: Chdir and stay there on program termination
Jun
10
reviewed Close Is it possible to write a 'fluent' style api in go?
Jun
10
reviewed Close The syntax and semantic of the Go compiler runtime
Jun
10
reviewed Close Increment struct variable in go
Jun
10
reviewed Leave Open Is there a cleaner way of error handling in a series of system calls?
1 2 3 4 5