Property serialization support

[musjj]

I really like using this pattern in my Unity classes:

[field: SerializeField]
public int Num { get; private set; }

This allows other classes to read the value, but not set it. The field: tag allows Unity to properly serialize the property for the inspector. But the same pattern doesn't work for Alchemy. For example:

using System;
using System.Collections.Generic;
using Alchemy.Serialization;
using UnityEngine;

[AlchemySerialize]
public partial class FooSO : ScriptableObject
{
    [field: AlchemySerializeField, NonSerialized]
    public HashSet<int> Nums { get; private set; }
}

The Nums property will not be visible in the inspector. But if you turn it into a normal field, it works:

[AlchemySerializeField, NonSerialized]
public HashSet<int> Nums;

Can support for properties be added for Alchemy too?

[paq]

Thanks for the suggestion! I can see the usefulness of supporting this pattern.

However, I’m a little hesitant to add support for it at the moment. In particular, I’d like to avoid relying on compiler-generated backing-field details such as <Property>k__BackingField.

With Unity moving toward CoreCLR, newer C# features such as field-backed custom properties may also become relevant in the future, and that could make the distinction between a property and its compiler-generated backing field more important.