mirror of https://github.com/k3s-io/k3s
57c3196914
In bringing back Clayton's PR piece-by-piece this was almost as easy to implement as his version, and is much more like what I think we should be doing. Specifically, any time which defines a .DeepCopy() method will have that method called preferentially. Otherwise we generate our own functions for deep-copying. This affected exactly one type - resource.Quantity. In applying this heuristic, several places in the generated code were simplified. To achieve this I had to convert types.Type.Methods from a slice to a map, which seems correct anyway (to do by-name lookups). |
||
|---|---|---|
| .. | ||
| amount.go | ||
| amount_test.go | ||
| generated.pb.go | ||
| generated.proto | ||
| math.go | ||
| math_test.go | ||
| quantity.go | ||
| quantity_example_test.go | ||
| quantity_proto.go | ||
| quantity_test.go | ||
| scale_int.go | ||
| scale_int_test.go | ||
| suffix.go | ||