I'm… sorry. I don't understand the purpose of this code listing.
In my original post I gave a solution to my own problem implemented in two
ways: with goroutines and channels, and with newcoro and coroswitch. If
you're trying to show me that I don't need either of those, that iter.Seq
is enough
You don’t need co routines if you have real concurrency. The generator use case is simply an optimization that wouldn’t be necessary if the concurrency model was more efficient - and there was a more expressive way to use it. I demonstrated on some Java boards that generators are easily implemented
On Mon, 2025-02-24 at 16:43 -0800, Robert Solomon wrote:
> I am interested in the gophers slack channel. How do I join it?
> #newbies would probably be the best fit for me
The invite link is here: https://invite.slack.golangbridge.org/
--
You received this message because you are subscribed t
I don't understand the tradeoffs involved, so I can't speak to the
hesitancy to release coroutines. They would probably be great
fun to play with. I imagine, however, they would provide ample foot-guns
too.
Perhaps that is a part of the reason. I find reading coroutine code in Lua,
for example,
I am interested in the gophers slack channel. How do I join it? #newbies
would probably be the best fit for me
On Monday, February 24, 2025 at 6:00:19 AM UTC-5 Dimas Prawira wrote:
> Hi Ahmed,
>
> You can join gophers slack channel there is #newbies channel and also
> #reviews channel if you
Thanks Ian, https://github.com/golang/go/issues/71939.
On Monday, 24 February 2025 at 20:54:27 UTC Ian Lance Taylor wrote:
> there wouldOn Mon, Feb 24, 2025 at 12:35 PM 'Paul Ruane' via
> golang-nuts wrote:
> >
> > I hit a problem today whereby a gRPC call did not come back with a
> status of c
there wouldOn Mon, Feb 24, 2025 at 12:35 PM 'Paul Ruane' via
golang-nuts wrote:
>
> I hit a problem today whereby a gRPC call did not come back with a status of
> cancelled, despite the request context being cancelled.
>
> Tracing it through I found that it was because of a failed DNS lookup and
Hi,
I hit a problem today whereby a gRPC call did not come back with a status
of cancelled, despite the request context being cancelled.
Tracing it through I found that it was because of a failed DNS lookup and
that the DNS code does not propagate the context cancelled error. I was
wondering i
Hello gophers,
We have tagged version v0.27.0 of golang.org/x/oauth2 in order to address a
security issue.
jws: unexpected memory consumption during token parsing
Version v0.27.0 of golang.org/x/oauth2 fixes a vulnerability in the
golang.org/x/oauth2/jws package which could cause a denial of s
Hello gophers,
We have tagged version v0.35.0 of golang.org/x/crypto in order to address a
security issue.
Version v0.35.0 of golang.org/x/crypto fixes a vulnerability in the
golang.org/x/crypto/ssh package which could cause a denial of service.
SSH servers which implement file transfer protoc
Hi Ahmed,
You can join gophers slack channel there is #newbies channel and also
#reviews channel if you already have project and want someone to help you
review your code or starting collaboration.
Regards
On Mon, Feb 24, 2025 at 2:40 AM Ahmed Faraz wrote:
> Hey everyone! I'm diving into Go
On Mon, Feb 24, 2025 at 9:20 AM Gavra wrote:
> I am not sure I understand. I have the issue reproducing only in production
> on a running instance...
Not mentioned in the OP. You can still try to write tests and/or
benchmarks that exhibit the same memory leak and then use them with
the -memprof
I am not sure I understand. I have the issue reproducing only in production
on a running instance...
On Sunday, 23 February 2025 at 15:22:27 UTC+2 Jan Mercl wrote:
> On Sun, Feb 23, 2025 at 1:12 PM Gavra wrote:
>
> > I have a heap profile that shows that many allocations are generated in
> a f
13 matches
Mail list logo
