https://blog.stackademic.com/after-disbanding-the-python-team-googles-go-team-faces-turmoil-12-year-project-leader-steps-down-29c4248ceb85
I could not read this article as it is behind a pay-wall.
But the title looks interesting, (and worrying if correct).
--
You received this message because yo
Its not clear to me if you are wanting to manipulation the ownership group
or the process group.
The ownership group is usually modified in the shell with chgrp. From a
program, you could
change it with https://pkg.go.dev/os#Chown
If you want a new process to have its own process group, you can
In the Interfaces section of "A Tour of Go" it says
"A value of interface type can hold any value that implements those
methods."
Shouldn't this be
"A variable of interface type can hold any value that implements those
methods."
Jon
--
You received this message because you are subscribed t
I for one would really like to see Go or TinyGo find a way to target eBPF
similar to how it can target WASM.
-Mike
> On Aug 14, 2024, at 4:40 PM, twp...@gmail.com wrote:
>
> For eBPF support in Go, see https://github.com/cilium/ebpf.
>
> AFAIK at the moment you can't compile Go to eBPF. The
For eBPF support in Go, see https://github.com/cilium/ebpf.
AFAIK at the moment you can't compile Go to eBPF. The most promising
approach is probably to adapt TinyGo to generate eBPF. There's an issue
that's been open for three years with no
activity: https://github.com/tinygo-org/tinygo/issues
Hope the question is not too OT for this group, if yes please just ignore
it and forgive me.
We're in the progress of migrating a somewhat-complex application
(https://github.com/evcc-io/evcc) from static, yaml-based configuration to
fully UI-controllable dynamic config. A running application m
My understanding is that optimizations like this are almost never worth it on
modern processors - the increased code size works against the modern branch
predictor and speculative executions - vs the single shared piece of code -
there is less possibilities and thus instructions to preload.
> O
> Won’t the speculative/parallel execution by most processors make the JMP
essentially a no-op?
I guess you are right, but this is true when JMP destination already in
instruction buffer. I guess most of these cases are when JMP leads to RET
inside on function, so indeed this optimization will h
Won’t the speculative/parallel execution by most processors make the JMP
essentially a no-op?
See
https://stackoverflow.com/questions/5127833/meaningful-cost-of-the-jump-instruction
> On Aug 14, 2024, at 11:31 AM, Arseny Samoylov
> wrote:
>
> Thank you for your answer!
>
> > We generally do
Thank you for your answer!
> We generally don't do optimizations like that directly on assembly.
I definitely agree. But this is also a pattern for generated code.
> and concerns about debuggability (can you set a breakpoint on each return
in the source?) also matter
This is an interesting probl
10 matches
Mail list logo