Currently, strings can be set to null, but other potentially nullable types cannot—including references, as well as value types such as int? or bool?. In this case, the call to SetPropertyValue() will be ignored entirely, and any preexisting value will be retained. This could result in unexpected, if not buggy, behavior. To remedy this, ideally the MemberDispatcher should be able to detect nullable types and, if a type is nullable, then permit the null value. If the type is not nullable, we should consider falling back to default.