Şafak Gür

I see your point. The argument docs imply inclusivity by stating the value represents "...min/max value the argument is **allowed to have**", but yeah I guess it wouldn't hurt to...

Thanks for the suggestion - I agree the new text validations would be useful! I think it would be safer to use runes instead of chars, and we could probably...

Sorry everyone, I neglected Guard a lot during the last year because of other responsibilities (the pandemic definitely didn't help). But I'm still working on v2, our next major version...

3352e34b627ed90957bef680bab480860aca35f4 adds most of the annotations. The remaining are string and URI guards. I couldn't find a way yet to transfer the nullability of an `ArgumentInfo`'s value when the type...

Hi Girts, I appreciate the readability benefits Martin Fowler mentions in the post you linked. It was a good read, so thank you for that. But I still have mixed...

Thanks, sensitive is actually much more fitting than secure. Now that you mention it, there are actually two flags in `ArgumentInfo`, the other being `Modified` . Although, atm it can...

Thank you for implementing this, I'll merge it into a v2-specific branch when there is one. I'm keeping the issue open until then.

Great suggestions, thank you. The reason I only included the inclusive checks first was that in a lot of codebases the limits are almost always stored inclusively, like `MaxValue`, `MinAge`,...

The following examples are not direct aliases as they accept different sets of parameters: > `Positive()` == `Min(0)` > `NotPositive` == `Max(0)` > `MinLength()` == `Member(_ => _.Length.Min())` Even the...

I apologize for the very late response. I also want to say that I really appreciate your contributions whether in the form of ideas, criticisms or pull requests. I'll be...