Re: [go-nuts] Re: C++ 11 to Golang convertor

I am reminded of someone once asked how to go from Burlington MA to Waltham, when what he really wanted to do was go from Burlington to Logan Airport. (For the uninformed, via Waltham is not generally how most would do it.) This conversation is thoughtfully covering all angles of the C++ to

Re: [go-nuts] What are the reasonable reasons to use pointers?

On Tuesday, January 1, 2019 at 9:13:44 AM UTC-8, Jan Mercl wrote: > > > On Tue, Jan 1, 2019 at 12:34 PM 伊藤和也 > > wrote: > > > What are the reasonable reasons to use pointers? Are pointers necessary? > > Yes, they're necessary in non-trivial programs. Without pointers any > program can use only

[go-nuts] Re: Go2 proposal: remove := operator (or remove variable shadowing)

Given all Go's narrow minded ideas for the sake of purity, := should be considered a vicious hack and removed from the language. Adding a simple var err At the top of a routine won't kill people. In my own experience, that construct is the single largest cause of trivial errors in Go

[go-nuts] Re: why does go reverse the order of name and type? "i int" vs "int i"

On Wednesday, September 19, 2018 at 10:30:11 PM UTC-7, Sathish VJ wrote: > > I've been asked this question a few times and I haven't been able to find > an answer. Why does go reverse the order of variable declaration: "i int" > vs "int i" > To match PL/I, of course. :-) -ahd- -- You

[go-nuts] Re: vertical search engine go concurrency

As Andre noted, I don't think you have provided sufficient information. I'd go further: *Stop*, Determine what you (and your developer) need to know. Decide what you want, and write a specification. If you have to ask "specification for what", make a list what you don't know. Does the

Re: [go-nuts] is this code thread safety?

What Jan said. I had started my own post before I realize other sane people checked in about the absurd colors. On Thursday, November 2, 2017 at 3:13:07 AM UTC-7, Jan Mercl wrote: > > On Thu, Nov 2, 2017 at 6:54 AM sheepbao > wrote: > > > the close function is thread

Re: [go-nuts] Tools for 80 column split for golang

I haven't edited on a true text mode terminal since 1992, but a column limit is still useful. This and the other Go standards for relatively fixed formatting are not its strong suit. On Wednesday, September 6, 2017 at 11:36:04 PM UTC-7, Jakob Borg wrote: > > On 7 Sep 2017, at 06:10, Sankar

Re: [go-nuts] Re: No Allman-Style, No go!

"And thirdly, the code is more what you'd call "guidelines" than actual rules." -- Captain Hector Barbossa On Saturday, July 29, 2017 at 10:37:11 AM UTC-7, ecstati...@gmail.com wrote: > > Sorry to repeat myself, but I think I wasn't clear enough, as many people > on this forum still don't