Vitalii Kryvenko

@MuhannadAlrusayni I'd like to clarify something more. What is the exact desired naming pattern in your case? For example, the current naming pattern in `bon` is the following: ```rust #[derive(bon::Builder)]...

As an example, the current Hashicorp [Vault API](https://docs.rs/vaultrs/latest/vaultrs/auth/aws/config/certificate/fn.create.html) uses functions with lots of positional parameters and it always accepts an `impl Client`. If only we had a way to generate...

Hi! The goal here is to provide the builder syntax when the user uses the trait as you mentioned in here: > and then be able to do ```rust let...

Thank you for the feedback ❤️, this should be landed in the next couple of weeks

Finally, this mega-PR is ready to merge. There are two low-effort features that I'd like to include in the upcomming release and the remaining work is left only for the...

I see what you mean. A separate file may not be then as good as I thought. > indicate patches lasting months or years In my case - it's just...

This is an intentional limitation of the standard derive macros intended for conservative protection from accidental breaking changes. Niko Matsakis' blog post calls it ["perfect derive"](https://smallcultfollowing.com/babysteps/blog/2022/04/12/implied-bounds-and-perfect-derive/) and explains in detail...

Hi. I assume by "expand" you refer to the [`cargo-expand`](https://github.com/dtolnay/cargo-expand) CLI tool? `cargo-expand` does lack the ability to do granual expansion of a specific macro - that's why I have...

Hi! The problem with such a feature is that the `.from(&T)` method needs to know that it should omit cloning the `username` field. The fact that it doesn't set it...

> Setters modify fields one at a time and don’t provide any guardrails around overall validity That makes sense to me. > Here’s an example of the kind of pattern...