[go-nuts] Re: Announcing gophersat, a SAT and Pseudo-Boolean solver, v1.0.0

2017-12-23 Thread Mandolyte
Fabien, you mention below that generics would help... I encourage you to make a fuller description of why/how generics would help and update this wiki page to point to it: https://github.com/golang/go/wiki/ExperienceReports#generics On Thursday, December 21, 2017 at 8:25:53 PM UTC-5, Fabien wro

[go-nuts] [mysql] 2017/12/23 11:09:37 packets.go:141: write tcp 127.0.0.1:20630->127.0.0.1:3306: write: broken pipe

2017-12-23 Thread jobs jobs
how to fix it? -- 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://groups.google.com/d/optou

[go-nuts] Re: Is go1.10beta1 a debug or unoptimized build? (possible regression)

2017-12-23 Thread jlindamo
Hard to get a public test case (private code), but I noticed with go10, the profiler puts 99% flat time in time.now. Did time.now change somehow? (pprof) top1 Showing nodes accounting for 2.11mins, 99.90% of 2.11mins total Dropped 26 nodes (cum <= 0.01mins) Showing top 1 nodes out of 10 fl

[go-nuts] Re: Is go1.10beta1 a debug or unoptimized build? (possible regression)

2017-12-23 Thread Daniel Theophanes
It did change. See https://golang.org/cl/76990 and https://github.com/golang/go/issues/20427 . The numbers you posted look larger then anticipated if it is the same one. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this g

[go-nuts] dep and versioning : how are conflicts dealt with ?

2017-12-23 Thread Fabien
Hello gophers, I'm currently trying to understand how versioning via dep currently works. There are a few things I don't understand. I know this is work in progress, and I don't know what's the current status about the famous diamond dependency issue : what happens when two dependencies A & B r

[go-nuts] Re: Announcing gophersat, a SAT and Pseudo-Boolean solver, v1.0.0

2017-12-23 Thread Fabien
Thanks for the link, I'll write a description of my problem. Le samedi 23 décembre 2017 13:29:59 UTC+1, Mandolyte a écrit : > > Fabien, you mention below that generics would help... I encourage you to > make a fuller description of why/how generics would help and update this > wiki page to point

[go-nuts] github repo names with "go-" prefix?

2017-12-23 Thread Tim Peoples
I've noticed a somewhat common practice of people naming their github repositories with a "go-" prefix (and then, of course, subsequently dropping the prefix in the actual package name) -- yet a similar naming scheme doesn't seem to be commonplace among many other languages. Is this recommende

[go-nuts] Re: github repo names with "go-" prefix?

2017-12-23 Thread Tim Peoples
[*yes, I'm responding to myself (I tend to do that sometimes)*] Hmm I suspect part of it may be coming from this PackagePublishing wiki page , where it's mentioned almost as a foregone conclusion yet may often be interpret

[go-nuts] Re: github repo names with "go-" prefix?

2017-12-23 Thread Dave Cheney
On Sunday, 24 December 2017 05:18:14 UTC+11, Tim Peoples wrote: > I've noticed a somewhat common practice of people naming their github > repositories with a "go-" prefix (and then, of course, subsequently dropping > the prefix in the actual package name) -- yet a similar naming scheme doesn't

[go-nuts] Re: [ANN] A Typed ORM Library

2017-12-23 Thread Alexey Palazhchenko
Hi, There is also https://github.com/go-reform/reform. –-– Alexey «AlekSi» Palazhchenko -- 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...@

Re: [go-nuts] github repo names with "go-" prefix?

2017-12-23 Thread Jakob Borg
On 23 Dec 2017, at 19:18, Tim Peoples wrote: > > I've noticed a somewhat common practice of people naming their github > repositories with a "go-" prefix (and then, of course, subsequently dropping > the prefix in the actual package name) -- yet a similar naming scheme doesn't > seem to be com

[go-nuts] Re: github repo names with "go-" prefix?

2017-12-23 Thread Tim Peoples
On Saturday, December 23, 2017 at 11:06:35 AM UTC-8, Dave Cheney wrote: > > On Sunday, 24 December 2017 05:18:14 UTC+11, Tim Peoples wrote: > > I've noticed a somewhat common practice of people naming their github > repositories with a "go-" prefix (and then, of course, subsequently > dropping

Re: [go-nuts] github repo names with "go-" prefix?

2017-12-23 Thread Tim Peoples
On Saturday, December 23, 2017 at 11:36:45 AM UTC-8, Jakob Borg wrote: > > On 23 Dec 2017, at 19:18, Tim Peoples > > wrote: > > > > I've noticed a somewhat common practice of people naming their github > repositories with a "go-" prefix (and then, of course, subsequently > dropping the prefi

[go-nuts] Re: [ANN] A Typed ORM Library

2017-12-23 Thread Eyal Posener
Nice stuff Alexey! thanks for this link, haven't seen it so far. Seems like we both got frustrated from the same issues with existing solutions :-) We took pretty different approaches to solve the typed-ORM problem though. The reform library has a larger run-time content, and keeps the generated

Re: [go-nuts] Re: golang for AI

2017-12-23 Thread Maurizio Totti
2017-12-22 15:08 GMT+01:00 Fabien : > I'm working in an AI research lab and use golang a lot, so I would tend to > say yes. We're working in the symbolic AI field though (ontologies, > constraint solving and that stuff), not machine learning. > > Le vendredi 22 décembre 2017 07:33:04 UTC+1, Lee Ric

Re: [go-nuts] [mysql] 2017/12/23 11:09:37 packets.go:141: write tcp 127.0.0.1:20630->127.0.0.1:3306: write: broken pipe

2017-12-23 Thread Justin Israel
On Sun, Dec 24, 2017, 2:22 AM jobs jobs wrote: > how to fix it? 2017/12/23 11:09:37 packets.go:141: write tcp 127.0.0.1:20630-> 127.0.0.1:3306: write: broken pipe You haven't provided any information or code, so anyone offering help is only going to be guessing. Try and figure out if you are

[go-nuts] Re: github repo names with "go-" prefix?

2017-12-23 Thread Manlio Perillo
Il giorno sabato 23 dicembre 2017 19:18:14 UTC+1, Tim Peoples ha scritto: > > > I've noticed a somewhat common practice of people naming their github > repositories with a "go-" prefix (and then, of course, subsequently > dropping the prefix in the actual package name) -- yet a similar naming >

Re: [go-nuts] github repo names with "go-" prefix?

2017-12-23 Thread Mariusz Gronczewski
On Saturday, December 23, 2017 at 8:48:37 PM UTC+1, Tim Peoples wrote: > > > Sadly, that is rarely the case. > > In fact, I often find authors with dozens of repos covering a number of > languages -- yet, only their "go" repos are named as such (repos with no > corresponding implementation in a

[go-nuts] Re: Is go1.10beta1 a debug or unoptimized build? (possible regression)

2017-12-23 Thread Krzysztof Kowalczyk
Most likely it's https://github.com/golang/go/commit/d8ff3d592088ef175222dbf69991887f0dd458d6#diff-b884a414ef2918cd3d75c6799cb62581 which seems to add fair amount of code to time.Now() You can see history of commits to that file with https://github.com/golang/go/commits/master/src/runtime/sys

[go-nuts] Re: dep and versioning : how are conflicts dealt with ?

2017-12-23 Thread David Collier-Brown
> > > A bit of an unresolved problem in several universes, one of which contains Go (;-)) I have some definite opinions: I grew up in a universe where it was resoilved in Multics, rediscoverd in Solaris and independantly rediscovered in Linux glibc. Way more information that you want in http

[go-nuts] Re: Is go1.10beta1 a debug or unoptimized build? (possible regression)

2017-12-23 Thread Jack
I ran the same benchmarks on my local linux NUC and the code actually had small performance improvements between 1.9 and 1.10 (some better some not). It appears to be isolated to running the benchmarks on my mac. On Saturday, December 23, 2017 at 5:38:31 PM UTC-6, Krzysztof Kowalczyk wrote: > >

[go-nuts] Re: Bcrypt isn't comparing stored password hash properly

2017-12-23 Thread Gabriel Simmer
I guess I should update this with the solution; As it turns out, the method I was using for getting user input was returning the user input in some funky way that I couldn't trace/replicate. I went with randomly generating the password, and that inserts/verifies just fine. On Tuesday, December