RE: [go-nuts] Re: Recover considered harmful

I had a few library functions which I couldn't decide on a "fits all" handling method. Often the decision is based on the caller's environment. So I decided to let the caller decide. // Panic holds an optional user function which is used to handle serious // run-time errors. If not set, the d

[go-nuts] All the Go project history, live in RAM

Gophers, Want to analyze the Go project's Git, GitHub, and Gerrit history? Here a package to make it easy: https://godoc.org/golang.org/x/build/maintner/godata See the example: https://godoc.org/golang.org/x/build/maintner/godata#example-Get--NumComments If you run that, it'll download

[go-nuts] "Selling" Go to Management

I would probably be more interested in: - What does Go bring to the table? What are its pros and cons compared to the current language being used in the company? - What is the future of Go? Do other people use it? I certainly don't want to invest in dead/dying technology. - What is the cost of m

Re: [go-nuts] Re: // go:generate won t work, //go:generate will

> ...but is not somehow invulnerable to forces of time and change. A new hope :D More seriously, friendly speaking, it might seem a bit ridiculous that the complete (or almost, i m not specialist in that area) go internals compiler was changed, but that this remains because of a decision. I e

[go-nuts] Re: [ANN] maintainer - Generate AUTHORS, CONTRIBUTING, and CHANGELOG for your GitHub repository.

False hopes :( https://github.com/gaocegege/maintainer#generate-changelogmd Wished it was made in go, but its redirecting to some ruby programs. Please let me know your intent for the changelog, i also did that, https://github.com/mh-cbon/changelog/ i m not against changing for new one if tha

[go-nuts] [ANN] maintainer - Generate AUTHORS, CONTRIBUTING, and CHANGELOG for your GitHub repository.

Maintainer is a CLI app which helps you to generate AUTHORS, CHANGELOG.md, CONTRIBUTING.md and so on based on the repository in GitHub. It makes your repository more contributor-friendly. You could get the docker image and have a try :) $ docker pull g

[go-nuts] Should we use frameworks like Go IRIS based on fasthttp to create foundation of my web application or do I start create framework from scratch

Should we use frameworks like Go IRIS based on fasthttp to create foundation of our web application or do we should start create our framework from scratch for our web application Where I can found good tutorials or documentation about advances topic in golang based on like syscall,exec,os

Re: [go-nuts] new topics vetted?

On Apr 29, 2017 11:07 PM, wrote: Are posts vetted before being accepted to golang-* groups? I'm pretty sure I just created a post on golang-dev, but I don't see it in recently posted topics. I don't want to create it again and spam the list with duplicate posts. Yes, the first time someone post

[go-nuts] testing net/http

A couple of weeks ago, I contributed a patch to net/http/fcgi (hooray!). It was simple to develop in this package. I added unit tests for my change and kept running go test inside that package to make sure my change was working. I also routinely ran

Re: [go-nuts] Re: // go:generate won t work, //go:generate will

On Sun, Apr 30, 2017 at 7:14 AM, wrote: > A satisfying solution, imho, involves a more in depth change, > which won t happen for reasons cited previously. > Don't be too sure about that. No reason why "generate" could not be changed/made redundant/more real/keyworded/etc. as part of the open and

[go-nuts] Re: // go:generate won t work, //go:generate will

Hi, its reasonable, but not satisfying, at least because lint/vet are not mandatory to build. A satisfying solution, imho, involves a more in depth change, which won t happen for reasons cited previously. Thanks. On Sunday, April 30, 2017 at 2:55:12 PM UTC+2, Caleb Doxsey wrote: > > Hi, > > Ju

Re: [go-nuts] Weird performance with exp/shiny

> An alternative approach is to separate your simulation loop and your rendering loop. or at the very least, calculate a timing delta to determine animation values. On Fri, Apr 28, 2017 at 9:48 PM Zellyn wrote: > Yes, the racy boolean access made me cringe but I was going for short :-) > > Your

[go-nuts] Re: // go:generate won t work, //go:generate will

Hi, Just a reminder that Go is an open source project. Although changing go:generate probably isn't going to happen, your comment about lint not catching the issue seemed reasonable to me. So I went ahead and implemented it and created a pull request: https://github.com/golang/lint/pull/291 -

[go-nuts] Re: "Selling" Go to Management

All those sound like good points, but it depending on how technical your mid/high level management are, you may want to adjust the wording. if your audience are very technical, go fmt, and not having to read/learn code style sounds great, if they are not very technical, they will care less abou

Re: [go-nuts] "Selling" Go to Management

Hi Miki, I would add the following two points: * Module system. This does not only help with the compilation speed, but has a bunch of other advantages. Like clear distinction between public/private data and functions. It also means, you don't have complex makefiles to build your system, the

[go-nuts] Re: NNTP mirror of this mailing list?

On Sun, 30 Apr 2017 09:24:36 +0100 Steve Mynott wrote: > I was wondering if there was a NNTP mirror of this mailing list > anywhere? > > I couldn't see it on nntp://news.gmane.org or anywhere similar after > a quick search. It's on Gmane - this reply is posted via Gmane, but it's not visible o

[go-nuts] Re: Question about type information for map and slice

Thanks a lot! 在 2017年4月30日星期日 UTC+8下午1:45:26，T L写道： > > > > On Sunday, April 30, 2017 at 10:54:07 AM UTC+8, feilengcui008 wrote: >> >> So, if i do this: >> //assign some var to interface type >> var i io.Reader = readerImpl >> i.Read(buf) >> >> the interface i's dynamic type infomation is

[go-nuts] NNTP mirror of this mailing list?

I was wondering if there was a NNTP mirror of this mailing list anywhere? I couldn't see it on nntp://news.gmane.org or anywhere similar after a quick search. -- 4096R/EA75174B Steve Mynott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To

Re: [go-nuts] // go:generate won t work, //go:generate will

You know i disagree, but i m sure it is yet a new hope for a new go :D On Saturday, April 29, 2017 at 10:39:36 PM UTC+2, Michael Jones wrote: > > [NOTE: an unofficial answer on Rob Pike's behalf] > > ...no, not organic growth, not oversight, not antique JCL inflexibility, > rather, a design choic

[go-nuts] Re: "Selling" Go to Management

And of course the community :) On Sunday, April 30, 2017 at 10:41:14 AM UTC+3, Miki Tebeka wrote: > > Hi, > > I'm giving a 1 hour talk on Go to mid/high level management. Here are the > points I thought to bring up (not in order), I'd appreciate any > comments/ideas. > > * The free lunch is over

[go-nuts] "Selling" Go to Management

Hi, I'm giving a 1 hour talk on Go to mid/high level management. Here are the points I thought to bring up (not in order), I'd appreciate any comments/ideas. * The free lunch is over - threads/async are difficult to work with * Small language - Easy to learn * Simple C based syntax