Open jdhoffa opened 7 months ago
I think that's what "deprecation" is intended for, no?
Yeah, Let's support them for another few months, and then internalize them.
Maybe more concretely, my question is:
I think this may be an appropriate strategy here
I think this is exactly what deprecate_soft()
is for, no? Anyone who calls the function directly sees the deprecation warning, anyone who uses it indirectly gets the expected result, some time later, we'll unexport them.
Sounds perfect!
Help achieved :-) thank you both.
These functions are currently exported, but I have no idea if anybody uses them. To some extent, it feels like we are committing ourselves to a maintenance burden for a decision made long ago.
I am curious if @jacobvjk thinks they are actively used (beyond when they are called in the body of
target_*
functions) Curious also how @AlexAxthelm and @cjyetman feel about this (not the details, but in general the process of deprecating a previously exported function)It feels like probably a bad idea/ bad form, but want your opinions here.
AB#9903