GoProxyProp.cs

using UnityEngine;
using System.Collections;

public class GoProxyProp<T> 
{
	public T property { get; set; }
    
	public GoProxyProp( T startValue )
	{
		property = startValue;
	}                                            
}

I think "value" would make more sense, since that what it is returning, not the name of the property being operated on.

I like this. I also think property is appropriate because we then have floatProp and vector2Prop method names.

I think "value" works a bit better too -- since it'd read something like:

GoProxyProp<float> someProgress;
//...
someProgress.value = 5;

Ok I agree with all that. How does this work then for you merging? Is there a way to merge this gist into the pull request? Or do you reject my request, I add this in, and then make a new request? I've not seen anyone make a code gist like this before from a pull request.

You handled it properly, this was just for a side conversation. Thanks!