I think when discussing tuples one should consider the [...]any type as an
alternative to []any. Arrays supports comparison, aren't boxed and are
generally more tuple-like. They can be used as map keys.
Of course, they're still not really type-safe. Structs solve that and also
support access by
Hi,
It works on the playground at least, https://go.dev/play/p/YZbgmezjSIV
Are you sure your server is listening on port 80? That's fairly uncommon
for service code and usually requires extra permissions.
If it's listening on another port, you'll have to specify that in the
browser as well (see
Hi,
Unfortunately, the only way to avoid having two sockets in this scenario,
is to listen to only one of 127.0.0.1 or ::1 and live with that it's only
one address family.
As you might've noticed, some tools still struggle with connecting to ::1
so listening to 127.0.0.1 is the most safe option
e 2023-09-20 meeting,
> which I've just done.
> There was no 2023-09-27 meeting due to GopherCon.
>
> Best,
> Russ
>
>
> On Mon, Oct 2, 2023 at 7:14 AM p...@morth.org wrote:
>
>> Hi,
>>
>> I might just be out of the loop, but it seems the review
Hi,
I might just be out of the loop, but it seems the review meeting notes are
no longer posted since a few weeks back,
https://github.com/golang/go/issues/33502
I really enjoyed reading these, it was a highlight of the week. Can I
expect these to be continued or has the process changed someho
Sarama's producer might qualify as interesting.
https://pkg.go.dev/github.com/Shopify/sarama#example-AsyncProducer-Select
You're supposed to produce messages on a channel while simultaneously
listening for acks (optional) and errors (mandatory) in the same select
loop.
Regards,
Per Johansson
O
It would actually be ambiguous in the very place they're required.
Consider this not completely unreasonable example:
https://go.dev/play/p/OL0uOnPZXju
Also, with generics it could be ambiguous in type parameters.
To summarize, parentheses are needed around the return types because
otherwise an
Hi!
It's not possible to decode this data without scanning it twice. It's a
flawed design where someone has chosen to make that restriction.
programming language doesn't matter.
The only way to avoid parsing it twice is to decode to a map[string]any and
then use that as-is. Which I suppose you
Hi,
I think you need to restructure your code, because what you're actually
doing is checking whether the pid is valid or not.
Since the pid is made invalid inside the Wait call (in the kernel), before
ProcessState is set, there's no way to do that safely.
Instead, you should avoid calling Wait
