Answers are grounded in this paper and cite their sources.
Deprecations are a common way to indicate that a given feature or API will not be available in subsequent versions of a library or framework. While raising deprecation warnings lets developers of libraries evolve their APIs, the developers of client applications often have to manually rewrite their applications to adapt to the deprecation (removal, new APIs. . . ). Some may use static analysis tools to support the rewriting. However, dynamically-typed languages or the use of reflective features often produce incorrect rewrite candidates. This is a costly activity that can lead to bug introductions.
No takes yet. Share an insight, caveat, or question.
Ducasse et al. (2022) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: