maxilozoz

The idea came from wanting to make nestd struct auto implement some interface, like kubernetes metadata field // pb by generate https://github.com/kubernetes/kubernetes/blob/25a3274a4f62be0d37937c069007cedb3116e467/staging/src/k8s.io/api/core/v1/generated.proto#L3017-L3021 // go struct https://github.com/kubernetes/kubernetes/blob/25a3274a4f62be0d37937c069007cedb3116e467/staging/src/k8s.io/api/core/v1/types.go#L3962-L3967 Of course here is...

> Annotating fields to change the Go representation of them is currently not supported, and we don't plan to support it. A common approach to alleviate this is to wrap...

It is also a good way to provide a tpl mechanism without polluting pb, https://entgo.io/docs/templates @aktau @puellanivis The generated code does not need to be changed, and the redundant code...

> What semantics are lost? This example is not very straightforward. Post some official explicit documentation and valid code examples to clarify which semantics are violated, thk. @puellanivis

> Given: > > ``` > // example message > message t1 { > string b = 1; > } > > message c { > t1 c1 = 1;...

`SHUT_RDWR` netlink return `operation not supported` ## method of setting recv timeout is also ok ## before edit, seeing that some goroutines did not exit ## after edit, look good

The author seems to be back. Check out the readme update.

+1

routes, err := h.RouteGet(net.ParseIP(localHostAddr)) if err != nil { return err } if len(routes) != 0 { for _, r := range routes { if r.Type != unix.RTN_LOCAL { continue...