Closed samreid closed 1 year ago
I found this is not a problem in some cases:
I sampled several new DerivedProperty
instantiation sites with options, and could not trigger this problem. I think it was due to the inconsistent callback signature, but that has been corrected in MSB by using deriveAny
. Closing.
@marlitas and I observed this code was not failing the type check:
Despite the excess properties at the bottom. Perhaps something about the overloaded DerivedProperty constructor is confusing it.