Matt Joiner

> Let's focus on 1 and 2 as actual production usages. What rqbit cares about it: > > 1. frequent access to info_hash for all kinds of purposes > 2....

> > I'm not sure it's worth it without creating a general abstraction like "WithRawValueAndHash" above. I'm not sure it's worth creating that abstraction either though - hard to tell...

> > I'm not sure it's worth it without creating a general abstraction like "WithRawValueAndHash" above. I'm not sure it's worth creating that abstraction either though - hard to tell...

I'm leaning toward 3 but without holding an intermediate value. I will update the PR in a day or two.

I made a good mess that I want to clean up when I get prove it will compile. I mentioned where I'm stuck above. The other difficulty I can see...

I can only add that yes, it would certainly be possible, and it would end up looking much like how I did it in https://github.com/anacrolix/torrent. It's not trivial as it...

I thought this was an issue with Xcode 15, I see it across all my Go projects.

Projects linking through cgo.

Yes, I'm referring to this general problem: https://github.com/golang/go/issues/61229#issuecomment-1988965927. However those are warnings, and I see OP has errors.

I can confirm this behaviour. It doesn't appear that broadcasting to all connected peers is a documented behaviour. It could be if the receiver tracked all received streams, and duplicated...