Re: [go-nuts] Re: How to refactor out this function

I think you should listen to James. He is quite right. Sometimes I am not thinking in English so a lot of people complain if I am the one who names things. And like James, I am always figuring out better ways to name things while making comments. RuneRead makes sense to me if I am thinking

Re: [go-nuts] How to update packages without duplicating distro packages

On Wed, 2018-08-08 at 21:57 +, Jakob Borg wrote: > What’s happening here is that you are pulling in more dependencies > than you expect. > > $ rm -rf ~/go $ go get -u > mvdan.cc/sh/cmd/shfmt > > In those commands, you downloaded the repo >

Re: [go-nuts] How to signal(sigint) blocking goroutine

Thanks for the info. I will look at the context information. On Wednesday, August 8, 2018 at 12:20:11 AM UTC-4, Ian Lance Taylor wrote: > > On Tue, Aug 7, 2018 at 7:02 PM, > > wrote: > > > > https://play.golang.org/p/d5n9bYmya3r > > > > I'm new to the go language and trying to figure out

Re: [go-nuts] CPU utilization spike during GC concurrent phase

On Wed, Aug 8, 2018 at 11:29 AM, brian.armstrong via golang-nuts wrote: > Hi golang-nuts, > > I've got a service that is seeing some confusing GC behavior. The behavior > manifests as long request latencies when the GC runs. At first I thought > this would just be stop-the-world behavior from the

Re: [go-nuts] How to update packages without duplicating distro packages

Just wondering, have you noticed my message? I think it's the only possible solution atm. Regards, четверг, 9 августа 2018 г., 1:09:40 UTC+3 пользователь Kevin Locke написал: > > On Wed, 2018-08-08 at 21:57 +, Jakob Borg wrote: > > What’s happening here is that you are pulling in more

Re: [go-nuts] Host two distinct modules in one git repo?

Paul, Since the issue affected only a specific Linux user running beta2, I suspected it was a caching issuen then used "go clean -modcache" (as suggested in https://github.com/golang/go/issues/26695) to fix it. And it worked. Unfortunately I don't know how to reproduce the caching (?) issue.

Re: [go-nuts] Host two distinct modules in one git repo?

> > > I can no longer see the issue in beta2 or beta3... AFAICT modules are > working like a charm. > Great! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

That's great to hear. Again, good luck! On Wednesday, August 8, 2018 at 3:50:56 PM UTC-4, Scott Cotton wrote: > > Oops, I forgot to CC golang-nuts.. > > > -- Forwarded message -- > From: Scott Cotton > > Date: 8 August 2018 at 21:48 > Subject: Re: [go-nuts] Re: [ANNOUNCE] for

[go-nuts] Re: [ANN] Pion-TURN, a TURN server designed with ease of use and extensibility in mind

(an example of two pions clients connecting to each other). can you help with the code On Monday, May 14, 2018 at 10:35:09 PM UTC+1, se...@pion.ly wrote: > > Hi list! > > I wrote a TURN server and would love to get feedback/share > https://github.com/pions/turn > > > If you aren't interested

Re: [go-nuts] How to update packages without duplicating distro packages

What’s happening here is that you are pulling in more dependencies than you expect. $ rm -rf ~/go $ go get -u mvdan.cc/sh/cmd/shfmt In those commands, you downloaded the repo mvdan.cc/sh and build cmd/shfmt that is part of it, while also

Re: [go-nuts] Re: Possible missing atomic load(s)/store(s) in runtime/chan.go?

On Sun, Aug 05, 2018 at 12:12:04PM -0700, Marvin Stenger wrote: > And my point was, that a slow path protected with a lock surely can execute > concurrently with a fast path not protected by that lock. So for the fast > path implementation one has to know what one is doing and if reordering >

[go-nuts] My trouble about GO interface

Hi everyone, I have some confusion about GO's interface: 1. Some different interface but with the same signature I have put an example here: https://github.com/vipally/glab/blob/master/lab12/walk_test.go The confusion is, there are two different interface filepath.Walker and pet.Walker.

Re: [go-nuts] Re: Nil Channels and Case Evaluation

According to this thread, for this program: package main func main() { var c chan struct{} select { case c <- f(): } } func f() struct{} { println("f called") return struct{}{} } The error message in the output: f called fatal error: all goroutines are asleep -

[go-nuts] Re: Keep Vendor folder on library Repository is Bad or Good practice.

I've never seen that happen before, but in case it does, only new environments will fail, i.e., those has been building fine will still be building fine. I.e. it's quite easy to correct. So I personally think that it is really a high price to pay for something that may *never* happen. Of

[go-nuts] Re: Keep Vendor folder on library Repository is Bad or Good practice.

https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/ Manlio On Wednesday, August 8, 2018 at 4:01:32 PM UTC+2, Tong Sun wrote: > > I've never seen that happen before, but in case it does, only new > environments will fail, i.e., those has been building fine will still be > building

Re: [go-nuts] Re: Nil Channels and Case Evaluation

i think the compiler has identified both problems correctly; c is nil (no cases) and nothing is receiving from c (deadlock). package main func main() { // var c chan struct{} c := make(chan struct{}) go func(x chan struct{}) { <-x }(c) select { case c <- f(): } } func f() struct{} { println("f

Re: [go-nuts] Re: Nil Channels and Case Evaluation

I did not say anything is incorrect. But the error message (no cases) is confusing and unclear because obviously there is a case there. Something like all channels of cases are nil is more clear or some other more proper/clear message. -- You received this message because you are subscribed

Re: [go-nuts] Re: Nil Channels and Case Evaluation

On Wed, Aug 8, 2018 at 11:15 AM Kaveh Shahbazian wrote: > But the error message (no cases) is confusing and unclear because obviously there is a case there. I don't think it's confusing. The run-time message obviously does not talk about the compile-time case presence but about no case the

[go-nuts] Re: Point by Reference in Golang

On Wednesday, 8 August 2018 00:35:06 UTC+2, paul...@gmail.com wrote: > > Hey guys, just looking for some direction on some good reference material > on GO's point by reference > Can you elaborate what "point by reference" is? V. -- You received this message because you are subscribed to the

Re: [go-nuts] How to update packages without duplicating distro packages

On Mon, Aug 6, 2018 at 6:12 AM Kevin Locke wrote: > Is there a way to update packages installed using `go get` without > duplicating packages that are distributed with Go or by my Linux > distribution? Assuming your $GOPATH is something like : $ cd /src; go get -u ./... -- -j -- You

[go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

this looks interesting, I've been using various go sox bindings for doing various sound processing (for machine learning) will your toolkit aim to provide similar functionality but in native go? On Wednesday, 8 August 2018 04:33:48 UTC+1, Scott Cotton wrote: > > Hello all, > > I am pleased to

[go-nuts] Re: Keep Vendor folder on library Repository is Bad or Good practice.

IMHO, the npm node packaging is just a mess -- I have several similar projects, and each has to pull in a HUGE pile of almost-identical dependencies, and not able to reuse between them at all. Whatever happening over there will not astonish me at all, including the infamous npm_left_pad_chaos

Re: [go-nuts] Re: Nil Channels and Case Evaluation

On Wed, Aug 8, 2018, at 04:40, Jan Mercl wrote: > On Wed, Aug 8, 2018 at 11:15 AM Kaveh Shahbazian > wrote: > > > But the error message (no cases) is confusing and unclear because > obviously there is a case there. > > I don't think it's confusing. The run-time message obviously does not

Re: [go-nuts] Host two distinct modules in one git repo?

Cole - apologies, things got busy in the last few weeks so this thread dropped off my radar. You've raised a number of questions in this thread; how many of these remain since the release of beta3? Or indeed the fixes that have hit go tip since beta3? Happy to work through anything that's

Re: [go-nuts] Host two distinct modules in one git repo?

Everton - apologies, things got rather busy and this thread dropped off my radar. Is it possible for you to test with the latest build of go from tip? There have been a number of fixes since beta3. Thanks On Thu, 26 Jul 2018 at 16:13, Everton Marques wrote: > > > Em quinta-feira, 26 de julho

Re: [go-nuts] Host two distinct modules in one git repo?

And incidentally, #modules on Gophers Slack will likely be a better place to work things through; it's got a great number of people helping/responding. On Wed, 8 Aug 2018 at 17:28, Paul Jolly wrote: > > Cole - apologies, things got busy in the last few weeks so this thread > dropped off my

Re: [go-nuts] Host two distinct modules in one git repo?

On Wed, Aug 8, 2018, at 11:29, Paul Jolly wrote: > And incidentally, #modules on Gophers Slack will likely be a better > place to work things through; it's got a great number of people > helping/responding. This thread is of great importance to a lot of people in the community, and the

Re: [go-nuts] Golang package docs site sluggish recently

This seems to happening again :( On 08/06/2018 12:26, Steven Hartland wrote: Thanks Chris appreciated, does indeed to be quick again :)     Regards     Steve On 08/06/2018 05:57, Chris Broadfoot wrote: Should be fast again now. I'm not sure what happened, but it appears the site search index

Re: [go-nuts] Re: Nil Channels and Case Evaluation

FWIW, either way the error message is not related to order of evaluation or anything. It always happens with nil-channels: https://play.golang.org/p/aBga7KFN30x On Wed, Aug 8, 2018 at 5:46 PM Sam Whited wrote: > > > On Wed, Aug 8, 2018, at 04:40, Jan Mercl wrote: > > On Wed, Aug 8, 2018 at

Re: [go-nuts] Host two distinct modules in one git repo?

On Wed, Aug 8, 2018, at 11:46, Paul Jolly wrote: > My suggestion would be that, in cases such as this thread, any > answers/insights derived from Slack be reported back to the go-nuts > thread, for the benefit of anyone else following along. This also has > the benefit of cutting out any noise

Re: [go-nuts] How to update packages without duplicating distro packages

On Wed, 2018-08-08 at 11:50 +0200, Jan Mercl wrote: > On Mon, Aug 6, 2018 at 6:12 AM Kevin Locke wrote: >> Is there a way to update packages installed using `go get` without >> duplicating packages that are distributed with Go or by my Linux >> distribution? > > Assuming your $GOPATH is

[go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

Hi, It is an open source project by and for gopher audiophiles. It could become your project :) There is a lot of functionality and planned functionality overlapping sox, but sox is pretty old and mostly in maintenance mode from what I understand. ZC is more geared toward library usage than

Re: [go-nuts] How to update packages without duplicating distro packages

On Wed, Aug 8, 2018 at 1:40 PM Kevin Locke wrote: > In my initial email $GOPATH was unset. Then I would try (unset $GOPATH defaults to being effectively the same as $HOME/go on nix) $ cd $HOME/go/src ; go get -u ./... (add -v and/or -x to see if something is actually happening) -- -j --

Re: [go-nuts] How to update packages without duplicating distro packages

On Wed, 2018-08-08 at 14:20 +0200, Jan Mercl wrote: > On Wed, Aug 8, 2018 at 1:40 PM Kevin Locke wrote: > > In my initial email $GOPATH was unset. > > Then I would try (unset $GOPATH defaults to being effectively the same as > $HOME/go on nix) > > $ cd $HOME/go/src ; go get -u ./... > > (add

[go-nuts] Re: How to refactor out this function

I cannot speak for the community, only for myself. I like to use NounVerb combinations that make sense with the package name. package.NounVerb() handles.HelloSend() I can then define the interface as VerbEr type HelloSender interface { HelloSend() } My son spent too

[go-nuts] [Code Review] Web App Boilerplate using the stdlib.

Howdy folks, made this project to see if you can really use the stdlib to write a web app server without using a framework and also give me a base for future web apps that I feel like building with a set of generic docs. It almost to the state where I can take it and actually start using it

[go-nuts] Re: How to refactor out this function

Thanks a lot for the input. Out of curiosity, for those action based functions, how would you name them using NounVerb combinations? For example, SayHi(), or PlayCards(), etc. thx On Wednesday, August 8, 2018 at 9:27:58 AM UTC-4, David Skinner wrote: > > I cannot speak for the community,

[go-nuts] Re: How to refactor out this function

HelloSender can SendHello(). Sometimes I find better ways of naming things while adding comments, because the act of describing what something is and does surfaces name-smells. HelloSender can HelloSend(). wat? HelloSend is a polite thing to say when you finally meet Send. io.RuneReader

[go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

Scott, Thank you for taking on this thorny and important area. I hope you manage to include the various interested parties, and reach a consensus that is both efficient and Go-like. Good luck! I look forward to reading updates on the project blog. Zellyn On Tuesday, August 7, 2018 at

Re: [go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

Scott, One thing that wasn't completely clear to me in the blog post was whether zikichombo was considering investigating a pure Go alsa compatible package. If I am not mistaken, right now, on Linux and on Darwin, the package actually performing audio stuff is using cgo. Also, while I understand

Re: [go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

One other question. I know you're aware of it because you mentioned it in the kickoff blog post, but do you intend to use the underlying types from https://github.go-audio/audio? Just curious, Zellyn On Wednesday, August 8, 2018 at 2:37:12 PM UTC-4, Sebastien Binet wrote: > > Scott, > > One

Re: [go-nuts] Re: [ANNOUNCE] for gopher audiophiles.

Sebastion, Given the nature of audio platforms, I do not think excluding cgo is feasible. There always seems to be very important layers in userland (though OS-privileged) There is a really neat package which does ALSA without the accompanying library already, github/yobert/alsa, whose headline

[go-nuts] CPU utilization spike during GC concurrent phase

Hi golang-nuts, I've got a service that is seeing some confusing GC behavior. The behavior manifests as long request latencies when the GC runs. At first I thought this would just be stop-the-world behavior from the GC, but as I dig into it more, it's clear that the STW phase is actually quite