-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
gh-117648: Remove unneeded and imprecise NEWS entry #117693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The speedup given in the PR was: For Windows, between 5% and 14% faster. For *nix, between 0% and 35% faster.
cc. @eendebakpt, @nineteendo |
Could you expand on the motivation for removing this news entry? We ask that all changes that will impact on users have a news entry attached to them. It seems to me that a 6% speedup for such a widely used function is a significant improvement that will be appreciated by users, who will therefore appreciate seeing a mention of it in the changelog. |
I am fine with either removing the news entry (the performance gain is real, but not huge), or making it more precise. Looking at the PR there is also a performance improvement for the
Any user who wants to know the details can lookup the PR. |
Yeah, that's certainly fair, "6%" is probably a bit misleading! Arguably a "false sense of precision" rather than "imprecision" ;) |
Oops, it's (implicitly given) in the commit message :)
|
Yep, I would be fine with a vaguer formulation. |
"FAKE precision!" 🧢 😆 |
Competing PR: |
Closed in favour of #117697 🔨 |
I'm incredibly sorry for all the caused trouble. According to my benchmark the performance increase was around 6% on Windows. |
No worries; we can amend NEWS entries.
I think there is no clear answer; it depends on the API, the use-case, and the performance impact. Sometimes a vague wording is fine. Other times, a more precise wording is warranted. |
I'm not sure a NEWS entry is needed for this change; alternatively, it should be made more accurate.