>> proportionalNotationDuration is not deprecated. Its type has been
>> changed, therefore the warning about not accepting a moment is correct.
>
> that's what I was saying. Wouldn't it have been better to treat it
> as a deprecated property with an appropriate warning, rather than as
> an API break with a warning instead of an error?
Dan implemented a solution for normal users, not for library
developers: if they run `convert-ly` on their input files, everything
will work just fine – they get warnings, but it will compile. Your
special situation, namely to write a version-agnostic library, is not
covered by this. AFAICS, it is not possible to satisfy both
situations at the same time.
> As it currently stands, however, I am forced to modify the code and
> have no benefit from the fact that the old code can still be
> compiled.
It is an inconvenience, yes, but I think that taking care of normal
users is more important.
Werner
