Re: [go-nuts] Sharing data via Mutex vs. Channel

Thanks that sounds reasonable to me -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://grou

[go-nuts] Sharing data via Mutex vs. Channel

Hi folks, somwhere on my golang journey ("don't k now where and when") I was teached that mutexes are very expensive and we should prefer to communicate over channels instead of working with mutexes. I trusted it until today. I explained it to our aprentice based on my knowledge and he asked me

[go-nuts] Tour Of go Page 8 in Basics does not work.

Hey List, is this the right place to get the tour of go fixed? The example on the following page https://tour.golang.org/basics/8 terminates unexpected with error process took to long. kind regards Reinhard Lüdiger -- You received this message because you are subscribed to the Google Group

[go-nuts] os.WriteFile not writing files in long running process

Maybe you are running out of sockets due to the missing close on the response body after read -- 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 golang-nuts+unsubsc

Re: [go-nuts] Is it possible to unmarshall Json by selecting the struct from a field in the Json?

Maybe https://github.com/mitchellh/mapstructure Will help you a bit -- 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 golang-nuts+unsubscr...@googlegroups.com. For

Re: [go-nuts] Re: Long running task in select case

Yea looks a bit easier 👍 Kind regards Reinhard -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, vis

Re: [go-nuts] Re: Long running task in select case

he effect of having "default" on line 24 as > empty? > > > On 18 March 2018 at 14:21, 'Reinhard Luediger' via golang-nuts < > golan...@googlegroups.com > wrote: > >> I came to the following solution for my long running tasks, using >> go-routine

Re: [go-nuts] Re: Long running task in select case

. März 2018 08:46:07 UTC+1 schrieb Sathish VJ: > > Looks like this last one works but also quite complicated. > > One question ... what is the effect of having "default" on line 24 as > empty? > > > On 18 March 2018 at 14:21, 'Reinhard Luediger' v

Re: [go-nuts] Re: Long running task in select case

. >> >> On 19 March 2018 at 07:44, Sathish VJ wrote: >> > Looks like this last one works but also quite complicated. >> > >> > One question ... what is the effect of having "default" on line 24 as >> empty? >> > >> >

[go-nuts] Re: Long running task in select case

I came to the following solution for my long running tasks, using go-routines & the context package, https://play.golang.org/p/2V_29lHt4Wn package main import ( "context" "fmt" "time" ) //LongRunningTask func LongRunningTask(ctx context.Context, index int) (err error) { // we'll si

Re: [go-nuts] Why should i use interface composistion

Unfortunately I have no tests yet. My plan is to use testify an mockery to generate tests for the Storage interface. I am aware of the fact that this only tests the app code . For testing the database methods we'll start integration tests against a real database., kind regards Reinhard Am D

Re: [go-nuts] Why should i use interface composistion

@all thx for your comments I think i understand now how to deal with the advise of small interfaces. -- 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 golang-nuts+

Re: [go-nuts] Why should i use interface composistion

hi, first of all thanks for your reply. Indeed, the interface arose from the necessity of testing. Have you expierience with a memory sql driver? Could you recommend one? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

Re: [go-nuts] Why should i use interface composistion

hi, firstnat all thanks for your reply. Indeed, the interface arose from the necessity of testing. Have you expierience with a memory sql driver? Could you recommend one? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] Why should i use interface composistion

Dear all, as far as I know it is recommended to keep actual interfaces as small as possible and to form bigger interfaces via interface composiston. Would be great if the community could advise me what the real benefits are. Lets say i want to create an interface for the database backend like t

[go-nuts] if you use sql.NullXYZ, what else do you find yourself doing to make coding easier (or make your code more readable, etc...)

For me it works perfect when I just define each nullable field as a pointer in the struct which represents a da base record. If the struct field is nil it will be null in the database and json encoding handles these fields also correctly -- You received this message because you are subscribed