iSynaptic/DotNetExtensionsImproved — comment on commit fa31f8c814877d2f8c5978e87adf26a594f3ce64
File:  line 0
By rebcabin:

What's the reason for replacing the Propagator auto property with "private set" with a "readonly" field? Is it just so that the field can be set ONLY in the constructor? If so, I think that's worthy, but... My knee-jerk technique is to use properties for anything public and never fields (though there are subtleties and debates about this -- I just spent half an hour perusing stackoverflow on the question :)

I don't think there is a way for an auto property to be settable only in a constructor. I'd be inclined to write the uglier code

private readonly Func> _Propagator;
public Func> Propagator { get {return _Propagator;} }