New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contrib/internal/httptrace uses "inet.af/netaddr" which in turns imports go4.org/unsafe/assume-no-moving-gc #1405
Comments
Hi @mrkagelui
This package has several features that are interesting to us that std "net" doesn't have. I'd say let's go ahead with the upgrade. |
thank you for the answer, will read |
#1406 was merged, closing. Thanks for this @mrkagelui. |
Is there a release planned including this fix? |
I think there's a milestone in that associated PR that says 1.41.0 |
I'm not very familiar with this repository's development and release timelines. |
We have tagged a release candidate for v1.41.0 which contains this fix:
The full release should be out by the end of the week |
Sweet. Thanks! |
an alternative is to force upgrade, |
Hi,
My app failed the test on the recent Go 1.19 because of
go4.org/unsafe/assume-no-moving-gc
, or rather because the current version used in this lib is not the latest, kindly check history of https://github.com/go4org/unsafe-assume-no-moving-gc/blob/main/untested.go for more info.Here's part of my
go mod why
:My question is: why is inet.af/netaddr used instead of the standard package "net"?
If we really need it, could we upgrade to the latest "inet.af/netaddr" to use the latest unsafe package? ref: inetaf/netaddr@377050f
The text was updated successfully, but these errors were encountered: