Russ Cox comments

Results 790 comments of


                                            Russ Cox

x/net/ipv{4,6}: adopt net/netip address types

What is the concrete API being proposed?

x/net/ipv{4,6}: adopt net/netip address types

If we pattern off of #45886, maybe we should define IPMsg matching the new UDPMsg (using its field names, not the ones in ipv4.Message) and add ReadIPMsgs and WriteIPMsgs methods...

x/net/ipv{4,6}: adopt net/netip address types

@martin-sucha @database64128 you commented on #45886. Any thoughts about my previous comment, essentially applying the same API here?

x/net/ipv{4,6}: adopt net/netip address types

If we apply the #45886 API then we get ``` type IPMsg struct { Buffer [][]byte // must be pre-allocated by caller to non-zero len; callee fills, re-slices elements Control...

x/net/ipv{4,6}: adopt net/netip address types

Add flags bits to the argument list and removed the populated by callee comment. Any other comments on the API? Does anyone object to adding this API?

x/net/ipv{4,6}: adopt net/netip address types

Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group

x/net/ipv{4,6}: adopt net/netip address types

No change in consensus, so **[accepted](https://go.dev/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group

proposal: make package initialization order within a series of import statements predictable and controllable

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

proposal: cmd/trace: support for perfetto

The current thing we use is unmaintained, and we have to move to something. Perfetto seems like the best game in town and it sounds like people here are generally...