Status on v2 of the library

[julealgon]

In another issue, it was mentioned that Guard v2 would probably be coming by March.

This question is to check on the current status of v2, and if there is any ETA for when it will be released.

Now that the .NET team has abandoned the !! null-check operator it would be nice to have Guard to unify all exception handling, however I'm hesitant in using it in its current form because it doesnt yet support caller expression names to automatically add the argument names to the exceptions: moving to Guard would be a downgrade compared to things like ArgumentNullException.ThrowIfNull for the common null handling.

Since !! was scheduled for .NET 7, I was contemplating the idea of just not using a library for exception throwing, as most of the exceptions we throw are ArgumentNullExceptions. With the decision to postpone that feature, I think it becomes valuable again to rely on Guard, but I wanted to do so without extra compromises.

[julealgon]

@safakgur are you not maintaining the library anymore? I'm not seeing any recent changes, and you are not replying to these issues.

If you decided to abandon it, please let the community know and potentially transfer your ownership to somebody else.

[sgf]

@safakgur

[safakgur]

I'm retiring Guard - I apologise for any inconvenience, and thank you for all the support. The readme has details.