Re: [go-nuts] Re: Go 1.8.1 is released

It's just politics! Simply use a VPN, Tor or a proxy to bypass the filter! On Sun, May 7, 2017 at 8:59 PM, ahochauwa wrote: > Hello, > > This issue might help you understand why: > https://github.com/golang/go/issues/12380 > > I hope one day Golang would be available without any restriction

Re: [go-nuts] Recover considered harmful

As Rob Pike said, if you don't let the real reason behind "panicing" die, then recovering is most logical thing to do in times of dire need! For instance, the Caddy server routinely uses *recover* to recover from panics but responsibily logs them during ServeHTTP because it has to provide ultimate

Re: [go-nuts] Go Fonts: request for feedback

t like it > with a link to a broad discussion on the subject of programming fonts. > Do you have anything that bothers you about them, maybe in > relationship with the list of fonts that you cited? What's not > "looking great" to you? > > On Fri, Feb 3, 20

Re: [go-nuts] Go Fonts: request for feedback

This is a nice initiative. But the font doesn't look great compared to what we already have in the OSS toolbelt, e.g. Roboto, Inconsolata, Fira, Open Sans, Office Code, etc. I was hoping for something more extravagant. Like most people on Hacker Ne

Re: [go-nuts] What is use for [:] of a slice?

[:] still has a use for arrays. https://play.golang.org/p/L0jfM46Zg4 On Tue, Jan 31, 2017 at 12:00 AM, Jan Mercl <0xj...@gmail.com> wrote: > On Mon, Jan 30, 2017 at 7:44 PM Andy Balholm > wrote: > > > Anyway, I can’t think of any reason to use [:] on a slice either. > > reasons[:]: https://play

Re: [go-nuts] Deleting the /r/golang subreddit

I don't think people realize the gravity of the situation, of what Brad pointed out. If I said something (which in reality I never said) and if someone responds back to me in a way (which they never did), it could have serious implications on the parties conversing on a topic -- particularly when

Re: [go-nuts] why this?

ically as the type assertion > would make it weird. > > On Thu, Sep 29, 2016, 07:02 T L wrote: > >> >> >> On Thursday, September 29, 2016 at 12:56:57 PM UTC+8, Micky wrote: >>> >>> The reason is directly stated in the Go language spec: >>> &

Re: [go-nuts] why this?

The reason is directly stated in the Go language spec: "If the type assertion holds, the value of the expression is the value stored in x and its type is T. If the type assertion is false, a run-time panic occurs." Here "hold" means if it succeeds.

Re: [go-nuts] image: algorithm to convert to grayscale

On Thu, Sep 29, 2016 at 3:19 AM, Rodolfo Carvalho wrote: > gift [3]: > y := 0.299*px.R + 0.587*px.G + 0.114*px.B > > I did not understand why image/color adds an extra 0.5 (500/1000) to y. > Could anybody give me a clue? > To directly answer your question: *GIFT also adds 0.5 to round off.

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

Thanks for the correction :-) On Thu, Sep 29, 2016 at 2:26 AM, Dave Cheney wrote: > s/go build/go install/g > > On Thursday, 29 September 2016 01:41:31 UTC+10, Micky wrote: >> >> go list ... >> go build ... >> >> It will build only if it it needs to! Other

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

go list ... go build ... It will build only if it it needs to! Otherwise add -a to force. On Wed, Sep 28, 2016 at 8:30 PM, Tim K wrote: > OK, so all that should happen is just re-install the binaries in > $GOPATH/bin. Does anyone have any tips or helper scripts that help automate > re-installin

Re: [go-nuts] What 5 things does Go need in 2017?

Go doesn't need anything. You just need to write more code ;) On Sun, Sep 11, 2016 at 6:43 PM, Mark Richman wrote: > I'm somewhat new to the community, and seek to understand its challenges > better. I'm also looking for opportunities to contribute. > > To that end, what 5 things does Go need in

Re: [go-nuts] Re: time.After faster than goroutine?

On Sun, Sep 4, 2016 at 1:23 PM, wrote: > This is consistent: https://play.golang.org/p/G-vXEBc1Ab Correct. Getting time in Playground returns constant output usually: Its RPC also does some sort of caching so it won't work for running time dependent tests like these: https://play.golang.org/p/u

Re: [go-nuts] A proposal for generic in go

I guess that's for diplomatic reasons. If you watch talks of core contributors then I believe you'll know what I mean :) On Tue, Jun 21, 2016 at 5:15 AM, Rodrigo Kochenburger wrote: > Micky, I'm not sure where you're quoting from but they never said it's never >

Re: [go-nuts] A proposal for generic in go

It's never going to happen! To quote the powers-to-be, "The language is done". Good luck! On Wed, Jun 15, 2016 at 6:04 AM, xingtao zhao wrote: > Here is my proposal for generic in go: > https://docs.google.com/document/d/1nO7D15c2B3eq2kF62C0yUs_UgpkyPL2zHhMAmlq1l98/edit?usp=sharing > > Many parts