Suggestion - DefaultValue

[Aragas]

Describe the feature

In my real life scenarios I have a concept of DefaultValue - it's mostly used in my custom TryParse scenarios, when the parsing failed, but the value still needs to be valid an initialized with something meaningful.
A possible implementation would be to have a static property DefaultValue, this way we also should be able to use with Static Abstract Members if needed for custom solutions.
The only note I have, since not every type has a default value, it would make sense to have a separate interface IVogenHasDefaultValue<>

[ValueObject<byte>]
[Instance("None", "0")]
public readonly partial record struct TenantId
{
    // Either manually or via Instance
    //public static readonly byte None = From(0);

    public static byte DefaultValue => None;
    // ...
    // Generated Code
    public static global::System.Boolean TryParse(global::System.ReadOnlySpan<byte> utf8Text, 
#if NETCOREAPP3_0_OR_GREATER
[global::System.Diagnostics.CodeAnalysis.NotNullWhen(true)]
#endif
 out TenantId result) {
        if(System.Byte.TryParse(utf8Text, out var __v)) {
            
            
            result = new TenantId(__v);
            return true;
        }

        result = DefaultValue; // instead of `= default`;
        return false;
    }
}

[SteveDunn]

Thanks for the feedback and apologies for the very slow response!

It could check for the special DefaultValue field (or property).

As a workaround, you could add your own TryParse and delegate to the generated one that one has a format provider. Something like:

    public static bool TryParse(ReadOnlySpan<byte> utf8Text, out TenantId result)
    {
        bool parsed = TryParse(utf8Text, CultureInfo.InvariantCulture,  out result);
        result = parsed ? result : None;

        return parsed;
    }

[Aragas]

Yea, I believe something like this is already used as a workaround by me, but it will be appreciated if there will be a default value behavior. Could be especially interesting for strings