Natalie Klestrup Röijezon
Natalie Klestrup Röijezon
To be honest, `k8s-openapi` already builds really slowly, and the second example looks cleaner to me anyway (aside from the `str::to_string` calls, but it's pretty un-rusty to hide those anyway...
I think this comes down to a larger issue about when things are `Option`al, and how we handle patches. Currently, (AFAIK) the policy is that all properties that are not...
I thought it would be possible to make `EyreContext` generic over the dynamic `Error` type, but that seems like a horrible rabbit hole. I don't think it's worth messing even...
Oh, that sounds like an interesting idea. To explain where I'm coming from a bit better.. I generally tend to prefer SNAFU for my error types (I guess I'm just...
`kube_rt` also has an issue where it currently doesn't support anyhow/eyre errors from the reconciler (because it requires the error type to `impl std::error::Error`), but I think that should be...
> I think there are ways to deal with this by leveraging Deref Yeah, or SNAFU's `AsErrorSource`. Then again, that still means that we lose the backtrace on the other...
Sorry, I was unclear. `kube_rt::controller` itself doesn't print any errors, but it wraps user errors to collect them with a bunch of system-generated errors: https://gitlab.com/teozkr/kube-rt/-/blob/45d66b631add448cc2e039f4b7e68152bcdef87e/src/controller.rs#L15-33, which it's then up to...
On nightly this mostly falls away, since SNAFU and eyre can both use `std::backtrace::Backtrace` and `std::error::Error::backtrace()` if asked to, but "just use nightly!" doesn't feel like a great message to...
> Lmk if you're interested in bikeshedding alternative approaches there. Absolutely. `kube_rt` is already an exercise in bikeshedding `kube::runtime`.. :P > I'm interested in learning more about how kube_rt is...
I guess one possible other approach would be to let the user control the ultimate error type, and just demand a `From` instance. I'm not a huge fan of using...