Arnav Singh

I would still like to know what these functions give you that just regular struct update syntax does not. In the issue you had written: >It doesn't compose well. >...

>a can be arbitrarily pre-populated. Eg. the higher level library might have already added common-labels, readiness/liveliness probes etc. Okay, that makes sense. >>It is very un-Rust-y to take borrows when...

>So for every type, we would define `fn merge_from(&mut Self, other: Self)` that would run `merge_from` recursively on all fields? > >Does this seem OK, or do you have any...

The types don't have setters or builders because all the members are `pub`.

I don't follow what setters and builders would allow you to do that setting the fields directly does not.

And the reason you can't set `.restart_policy`, call `.containers.push()`, do whatever `override_with` is supposed to do... is?

`k8s-openapi-codegen-common` contains the code for understanding a swagger spec, and `k8s-openapi-codegen` uses it to emit the `k8s-openapi` crate. So you can try copying `k8s-openapi-codegen-common` and changing its templates to instead...

I think most of those people will stop wanting it after they see the crate takes 50% more time to compile when they enable the feature. That's why this crate...

>Is this something you'd consider accepting PRs for? Yes, but please make sure to add tests for it because it wouldn't get exercised otherwise.

As the error tells you, you still have k8s-openapi 0.11.0 somewhere in your lockfile, so read it to figure out what's pulling it in.