Re: Deprecate posix_times

Hi On 10/18/23 09:00, Christian Schneider wrote:

My question here would be: Is there sufficient reason to remove this function and introduce a BC break, i.e. is the implementation code hard to maintain or does the function cause security issues? Unless that is the case I'd leave it unchanged and just add a note to the documentation that people might want to consider using getrusage() instead.

If a function cannot be safely or correctly used at all, then it shouldn't exist, especially if there are working alternatives [1]. Expecting users to find a warning in the docs to learn that they should "never" use a function is not good developer experience. Best regards Tim Düsterhus