Chars restriction for PropertyPath

[FoggyFinder]

Currently there are next restrictions to the symbols:

        private static bool IsValidIdentifierChar(char c)
        {
            if (IsValidIdentifierStart(c))
            {
                return true;
            }
            else
            {
                var cat = CharUnicodeInfo.GetUnicodeCategory(c);
                return cat == UnicodeCategory.NonSpacingMark ||
                       cat == UnicodeCategory.SpacingCombiningMark ||
                       cat == UnicodeCategory.ConnectorPunctuation ||
                       cat == UnicodeCategory.Format ||
                       cat == UnicodeCategory.DecimalDigitNumber;
            }
        }

Source

These constraints are definitely more strict than WPF has. For example, UnicodeCategory.DashPunctuation is valid for WPF.

[grokys]

Why would you need to use a dash in a property path? Is there anywhere a dash is valid in a .NET property name?

Also by allowing dashes, we'd be ruling out the future possibility for allowing mathematical expressions in a binding.

[FoggyFinder]

Is there anywhere a dash is valid in a .NET property name?

I don't think so. Not sure although.

Anyway, properties with dashes might be exposed as helper properties in some libraries.
For example, in Gjallarhorn.Bindable:

    let getErrorsPropertyName propertyName =
        propertyName + "-" + "Errors"
    let getValidPropertyName propertyName =
        propertyName + "-" + "IsValid"

Source

So it won't work for Avalonia as for WPF.

If dashes won't be allowed in principle then I'll open issue there to discuss how to handle it better. I just want to be sure that it is intentional restriction and not bug or something.

[FoggyFinder]

Closing this one since that not a bug and last reply was long ago.