Re: [go-nuts] Re: Rule-swarm attacks can outdo deep reasoning

Quoting Lucio (2018-10-04 23:19:48) >On Tuesday, 2 October 2018 15:21:08 UTC+2, Eric Raymond wrote: > >Is promised in the thread on pytogo, I have blogged on the general >topic of rule-swarm attacks in the domain of language transformation. >[1]http://esr.ibiblio.org/?p=8153 > >

[go-nuts] Re: Rule-swarm attacks can outdo deep reasoning

On Tuesday, 2 October 2018 15:21:08 UTC+2, Eric Raymond wrote: > > Is promised in the thread on pytogo, I have blogged on the general topic > of rule-swarm attacks in the domain of language transformation. > > http://esr.ibiblio.org/?p=8153 > There's so much in your blog post I would like to ad

[go-nuts] Re: Rule-swarm attacks can outdo deep reasoning

On Tuesday, 2 October 2018 15:21:08 UTC+2, Eric Raymond wrote: > > Is promised in the thread on pytogo, I have blogged on the general topic > of rule-swarm attacks in the domain of language transformation. > > http://esr.ibiblio.org/?p=8153 > I'm no pragmatist, I bow to ESR for shining that lig

Re: [go-nuts] Announcing pytogo. a crude but surprisingly effective Python to Go translator

As an amateur, I find this stuff fascinating. My biggest fear is that I might miss an episode. As far as the competing approaches go, my gut feeling is that if we don't see the convergence, it is simply too early in the game. Somehow, mathematical notations seem to have defeating the third law

Re: [go-nuts] Re: deadlock "runtime.(*sigctx).preparePanic"

On Thu, Oct 4, 2018 at 1:35 PM, wrote: > > Panic was caused by a stack smash, default cgo thread stack size was too > small. My fix is to change cgo thread stack size at compile time by patching > gcc_darwin_amd64.c, _cgo_sys_thread_start: > > 40a41,45 >> #ifdef CGO_STACK_SIZE >> size = CGO_S

[go-nuts] Re: deadlock "runtime.(*sigctx).preparePanic"

Panic was caused by a stack smash, default cgo thread stack size was too small. My fix is to change cgo thread stack size at compile time by patching gcc_darwin_amd64.c, _cgo_sys_thread_start: 40a41,45 > #ifdef CGO_STACK_SIZE > size = CGO_STACK_SIZE; > pthread_attr_setstacksize(&attr, si

Re: [go-nuts] Traverse directory without infinite loops while following links

* EricR [181004 13:33]: > Hi! I'm new to Go and need to do something with each file in directories. > Symlinks need to be followed. I've tried filepath and a few popular > libraries and they either crash with segfaults on my system, do not follow > symlinks or do not prevent infinite loops. >

[go-nuts] Participate in the Go 2018 Company Questionnaire

The Go project wants to hear from you! We need your help to create the best programming language for developing simple, reliable, and scalable software. To do this, we need to better understand how companies are using Go. Please help by participating in a 7-minute company questionnaire. *Who

Re: [go-nuts] Announcing pytogo. a crude but surprisingly effective Python to Go translator

I also, for this kind of things that seems to be coming out once in a while, tend to start from AST and a "pretty printer". This has limitations since AST doesn't give you type informations (not that it matters much for Python) but it's good for a "first pass" of translation. Here is my latest att

[go-nuts] Traverse directory without infinite loops while following links

Hi! I'm new to Go and need to do something with each file in directories. Symlinks need to be followed. I've tried filepath and a few popular libraries and they either crash with segfaults on my system, do not follow symlinks or do not prevent infinite loops. Is there a directory walking librar

[go-nuts] Re: packet filter for VM in golang

In a data center, many operator meter each VM's packet to the Internet for billing In a SR-IOV setup, the NIC would have to meter packets for all VMs being served by the NIC (or smartNIC). A NIC such as the one from Netronome supports BFP in their NIC NPU. There are frontends in C and golang

[go-nuts] Re: packet filter for VM in golang

Yes. But where do you place that bpf code? Where will it run? What packets will it monitor? eBPF is run in a virtual machine _in_the_kernel_. So a "VM using SR-IOV" bypasses this, also. Your monitor must be running in each guest VM, or you must NOT allow SR-IOV - that bypasses the host's kernel

[go-nuts] Re: packet filter for VM in golang

Right. However, if a VM is using SR-IOV which connects the VM directly to the NIC, the kernel is bypassed. Since sending my email, I also found a packet filter in golang: https://godoc.org/golang.org/x/net/bpf I have tested the above code yet. Thanks, Hemant On Thursday, October 4, 2018

Re: [go-nuts] Announcing pytogo. a crude but surprisingly effective Python to Go translator

On Thursday, October 4, 2018 at 4:26:44 AM UTC-4, Peter Waller wrote: > > My approach is a bit different, and works by printing the Python AST in > Go. There is an overlap in our philosophy of 'produce standalone code' and > 'help a human do the translation into idiomatic Go'. However, mine was

[go-nuts] Re: Rule-swarm attacks can outdo deep reasoning

On Wednesday, October 3, 2018 at 4:05:30 PM UTC-4, Michael Ellis wrote: > > Nice writeup. Thanks. Based on today's xkcd , I > think Randall Munroe must have read it, too ;-) > Seems likely. Randall and I have been friendly. -- You received this message because you

Re: [go-nuts] Announcing pytogo. a crude but surprisingly effective Python to Go translator

Hi Eric, I played around with some similar ideas a while back - I just blew the dust off it and published it here: https://github.com/pwaller/pp2g My approach is a bit different, and works by printing the Python AST in Go. There is an overlap in our philosophy of 'produce standalone code' and 'he