Oct. 25, 2018
6:10 p.m.
On Thu, Oct 25, 2018 at 11:48 PM Joseph Fox-Rabinovitz <jfoxrabinovitz@gmail.com> wrote:
In that vein, would it be advisable to re-implement them as aliases for the correctly behaving functions instead?
- Joe
Wouldn't "probably, can't be changed without breaking external code" still apply? As I understand the suggestion for _deprecation_ is only because there's (a lot of) code relying on the current behaviour (or at least there's risk). András