[go-nuts] Looking for help on a hobby robotics project

I build and program robots as a hobby. And I'm quite new to Go. I'm currently trying to adapt an open source Windows based Go SLAM program written by Mikael Berg in Norway as his Master's thesis for a laptop on wheels style robot. The program, written primarily in Go, also uses a JavaScript

[go-nuts] Re: interactive debugger for go ??

Hi, I've been frustrated by this for ages, I was using IntelliJ on a Mac with the Go plugin as that's what everyone on my team was using. The debuggers (or their UI impls were super flaky - Delve and GDB), and I would steer clear for now unless patience and tenacity are your middle names. I

Re: [go-nuts] Re: Float32 math and slice arithmetics using SIMD

> > Take for instance the PSHUFB instruction, which allows a very fast > [16]byte lookup in SSSE3 capable machines. This is helpful in various ways, > but if it isn't available, it will have to commit the XMM register to > memory and do 16 lookups, which is at least an order of magnitude

Re: [go-nuts] Freetype performance

I don't know if it is cached or not, but taking 15ms for rendering 300 characters, most of them spaces, size 12 (102 dpi) on a Intel 2500 seems to much. Here is the profiling:

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

Oh, I agree. The aggressive/threatening email was an unwarranted, disproportioned response. I'm just trying to understand where the strawmans/tangents (or what I perceive as, willing to be corrected) are coming from. And I didn't list all. Surgical arguments > narratives. On 29/10/16 01:31,

Re: [go-nuts] Re: Float32 math and slice arithmetics using SIMD

just, Machine Code, may be a less common term now. strictly you might say the 'text' being generated here is assembly, and it becomes m/c 'numbers' after the assembler, but since its just a one-one relationship, there isn't really much of a conceptual difference. On Friday, 28 October 2016

Re: [go-nuts] Re: Float32 math and slice arithmetics using SIMD

> Yes, speeding up an accumulation step, described at > > https://medium.com/@raphlinus/inside-the-fastest-font-renderer-in-the-world-75ae5270c445#.qz8jram0o > > > The generated code are SIMD implementations of very simple Go functions. > > For example, the fixedAccumulateOpSrcSIMD function

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

On Fri, Oct 28, 2016 at 2:41 PM, Aldrin Leal wrote: > Regardless, I wonder what would be the action taken if it were more than a > "warning". > > Would the CoC people issue a "SP" declaration? An Index Comunitum > Prohibitorum? Why wonder? You can read for yourself at

Re: [go-nuts] CGO: How to link static library across dependent packages?

On Wed, Oct 26, 2016 at 11:15 PM, wrote: > > Two of my packages have dependency on the same C library. I have linked them > successfully using the LDFLAGS directives. > > But I'm facing a multiple definitions error when linking my project > executable > > > Here is an

Re: [go-nuts] go vendoring build issue

Thanks Justin. I double-checked - every usage imports it as k8s.io/kubernetes/pkg/api . On Friday, October 28, 2016 at 3:38:47 PM UTC-4, Justin Israel wrote: > > > > On Sat, 29

[go-nuts] Re: Is ROC part of 1.8?

We are still actively working on ROC. Unfortunately it will not be part of 1.8. On Thursday, October 27, 2016 at 1:17:44 PM UTC-4, Chandra Sekar S wrote: > > Is the request-oriented GC slated to be included in the 1.8 release? > > -- > Chandra Sekar.S > -- You received this message because

Re: [go-nuts] Re: Go interface

Thanks for the replies. Sincerely, Arafath M On Fri, Oct 28, 2016 at 6:25 AM, Henry wrote: > Hi, > > I usually use the following pattern when creating a type. In your case, it > would be as follows: > > interface Animal { > Eat() > Travel() > } > > interface

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

> > The original e-mail is clear that it was passing along a complaint > from someone else. That person was following the procedure outlined > in Go's code of conduct (https://golang.org/conduct). > In bold, the CoC calls out, "Note that the goal of the Code of Conduct and the Working Group is

Re: [go-nuts] Re: Stopping a server

On Fri, Oct 28, 2016 at 8:15 AM, Peter Mogensen wrote: > > The point being that it's up to the user of the interface how to specific > Server implementation should work. > Yes, of course, but an interface with just two methods (Serve / Stop) is not enough to provide race-free

Re: [go-nuts] Re: Stopping a server

On 2016-10-28 09:09, Nick Patavalis wrote: On Fri, Oct 28, 2016 at 8:15 AM, Peter Mogensen wrote: The point being that it's up to the user of the interface how to specific Server implementation should work. Yes, of course, but an interface with just two methods (Serve /

[go-nuts] Re: golang too many json unmarshal trigger gc frequency to many

On Friday, 28 October 2016 07:36:20 UTC+2, Erik Dubbelboer wrote: > > Try https://github.com/pquerna/ffjson to improve speed and reduce garbage > generation. This in combination with sync.Pool will increase your > throughput by A LOT. > Also try out http://ugorji.net/blog/go-codec-primer -

Re: [go-nuts] Re: Stopping a server

FWIW we often use an interface named Worker for long lived processes, including servers: type Worker interface { Kill() Wait() error } Kill asks the worker to die but doesn't block. Wait waits for the worker to die and returns any error encountered while running.

Re: [go-nuts] Re: Stopping a server

On 2016-10-28 10:37, roger peppe wrote: FWIW we often use an interface named Worker for long lived processes, including servers: type Worker interface { Kill() Wait() error } Kill asks the worker to die but doesn't block. Wait waits for the worker to die and returns

Re: [go-nuts] HTTP2 Runtime panic while Migrating an Application from Go 1.4.1 to 1.6.2

Hallo Brad, ... thanks for the reply. The original post went under 6 weeks ago and I had forgotten it, sorry. We currently have a culprit and a work around, and your half right. The postgres in the backend was running out of connections and the errors were not getting to the client. The

Re: [go-nuts] Re: Stopping a server

On Oct 28, 2016 14:48, "Peter Mogensen" wrote: > > So ... bottom line ... defining Server objects as one-shot/single-use allows you to define the Kill()/Shutdown() semantics to simply exhaust that single-use. (an being idempotent) ... making it irrelevant whether the server has

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

I'm with you on pushing back. It keeps those in controlling positions from being too self-convenient in exercising said control. However, it is only effective when the person doing that is reasoned and does not resort to tangents, strawmans, and overreaction. - Why bring generics into this?

Re: [go-nuts] Tooling experience feedback

ah, good to know, thanks. However, it is not something one immediately finds out just by looking at the output of "go help". Afaics, "go doc go" isn't even mentioned (as an example or otherwise) in "go help doc". On 27 October 2016 at 17:56, Russ Cox wrote: > FWIW 'go help all'

[go-nuts] go vendoring build issue

I am trying to build my project with *go build *and running into an error where it seems like the type resolution of a method happens with the vendored path and the invocation of the method is happening with the actual package present in GOPATH. client/nuageclusterclient.go:129: cannot use

Re: [go-nuts] Re: Stopping a server

On Oct 28, 2016 14:32, "roger peppe" wrote: > > Yes, that's right. The main difference from a context is that a context provides > no way to know when things shut down. This, I think, is by design - things > like ErrGroup provide that functionality when needed. Yes, exactly.

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

On 10/27/2016 03:33 PM, charras...@gmail.com wrote: > code of conduct workers should work on adding generics to compilers True. But, consider this: if they /could/ accomplish that feat, then they wouldn't be wasting time policing people's thoughts and "propriety". What have thought puritans

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

Oh I didn't mean to direct it to you. Inbox wouldn't let me edit the recipient list without harming my phone... You make good points though so I am glad I did! ☺️ On Fri, Oct 28, 2016, 17:34 Kiki Sugiaman wrote: > Oh, I agree. The aggressive/threatening email was an

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

No harm done, I've done worse with a desktop. Hah! On 29/10/16 02:47, Henrik Johansson wrote: Oh I didn't mean to direct it to you. Inbox wouldn't let me edit the recipient list without harming my phone... You make good points though so I am glad I did! ☺️ -- You received this message

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

On Thu, Oct 27, 2016 at 9:11 AM, Nate Finch wrote: > It seems like most of the problem with this whole situation comes from the > wording of the "warning" > > Please consider this a warning from the Code of Conduct working group. >> > > "consider this a warning" can be

[go-nuts] Re: go vendoring build issue

I recall trying to use the Kubernetes client code some months ago. These sorts of errors ring a bell. You might try building the Kubernetes project as a standalone. It's a huge kitchen sink of a thing and not terribly friendly for someone who wants to do something relatively basic. On Friday,

Re: [go-nuts] CGO: How to link static library across dependent packages?

Hi Ian, Here is the build output -- FYI -- The path: //goLang/goCode/src/eventbridge/EventBridge.c was where I had compiled the C library using the gcc toolchain. I copied this compiled library to my project and statically linked it. Path to my project is at //goLang/goCode/src/agent/

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

The problem isn't the CoC or that the group it responded to a complaint but that it right away started with a very aggressive warning email. Why not talk to Aram like human being explaining the situation. This would have given him a chance to resolve it on his own. Seems like a much simpler and

Re: [go-nuts] HTTP2 Runtime panic while Migrating an Application from Go 1.4.1 to 1.6.2

Sounds like you need to understand your defer issue before making any changes or updating versions. On Oct 28, 2016 6:33 AM, "Nigel Vickers" wrote: > Hallo Brad, > > ... thanks for the reply. The original post went under 6 weeks ago and I > had forgotten it, sorry. We

Re: [go-nuts] Freetype performance

On Sat, Oct 29, 2016 at 2:11 AM, David M. wrote: > Here is the profiling: Ah, in package freetype, face.Glyph results (glyph images) are cached but face.GlyphAdvance and face.Kern results are not. Thanks for the bug report, I filed

Re: [go-nuts] Re: Stopping a server

On 2016-10-28 13:32, roger peppe wrote: On 28 October 2016 at 11:03, Nick Patavalis wrote: In fact the worker "w" is a single-use thing much like a context. Yes, that's right. The main difference from a context is that a context provides no way to know when things

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

On Fri, Oct 28, 2016 at 1:02 AM, wrote: > > That being said, I personally find the fact that someone is paid to sit > around censoring really mild messages and making feel good rules that do > more harm than good kind of gross. Doesn't Google have better things to >

Re: [go-nuts] Re: Stalking people online for thought crimes! This is what the Go project has succumbed to!

This person is old enough to answer me himself, he doesn't need your help for that , I wasn't talking to you so mind your business. And how about you dump your patronizing tone and go back to your own business ? Your comment is useless. Le vendredi 28 octobre 2016 13:30:33 UTC+2, Manuel Amador

[go-nuts] Re: HTTP2 Runtime panic while Migrating an Application from Go 1.4.1 to 1.6.2

Hallo Andras, ... thanks, but it's nothing to do with Gowut. See my reply to Brad. Rgs Nigel On Thursday, 27 October 2016 22:51:01 UTC+2, András Belicza wrote: > > Latest version of Gowut is 1.1.2. Is the problem persist with Gowut 1.1.2? > > >> -- You received this message because you are