Kevin Schaal

Hi, thank you very much for this suggestion, I think a `FluentSkippable` attribute would be a great addition to the library. The meaning of the attribute is easy to grasp...

> Also if you would return an object for even the first step, it would allow to use the options pattern easier: > > ```cs > void DoSomething(Action builder) {...

I have thought more about the `FluentSkippable` attribute in the context of forks, and I believe it is correct to annotate individual members and methods. Consider a builder with the...

Hi Nikhil, thank you very much, I am glad that you find the library useful. A port to Java, one of the most used languages, seems to be very useful,...

Hi, thank you very much for reporting this observation. I think this is an interesting topic for many people. `Carcasse` and `Carasso` are good matches for the query `carcasso` because...

Hi @leeoniya, thank you very much for your input and for adding this project to the demo / benchmark. Your work is really nice! I have added a comment to...

Thank you for pointing this out! The `UnsafeAccessorAttribute` is indeed a great feature, and I would love to eliminate the reflection code. However, I plan to stick with .NET 6...

Thank you for your request! Inheritance is the next feature I would like to look into. Best regards, Kevin

Hi @Sam13, That is a very good question and I currently don't have a good answer to this use case. Constructors are not taken into account by the Fluent API...

Hi @Sam13, Thank you for this! What you want to achieve is already possible like so: ```cs [FluentApi] public class Student { [FluentMember(0)] public string FirstName { get; private set;...