Hello Saul, > I don't want to speak for Dan, but I believe the objective is to get user > code moved over to actually using exact rationals rather than moments for > these properties, not just to allow the use of exact rationals in addition > to moments.
This is not what I talked about. My point is: A deprecated property you’d usually get when an interface has been considered as not optimal and is changed, but you give the user time to adjust, allowing the old interface to still be used. This is not what is happening here. Here a new interface is introduced (namely `proportionalNotationDurationAsMoment`) as deprecated property. Essentially this is telling the user: Here is a new feature, but you should not actually use it, because it has been considered bad and will be removed in a future release. I just don’t quite get why this has been done. It is not adding any compatibility, because the original interface has been broken, and now we are telling users: Instead of the old interface use this deprecated new interface, instead of just: Use the same interface, but you will need to add a type conversion. Cheers, Valentin
signature.asc
Description: This is a digitally signed message part.
