-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-128563: Clarify wording in Whats new for Tail call #130911
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
|
@@ -301,11 +301,11 @@ For further information on how to build Python, see | |||
cautiously revised down to 3-5%. While we expect performance results to be better |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for updating the docs! it's been interesting following along the journey :-)
maybe a silly question, why do we expect performance numbers to be better than what we report?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The computed goto bug in theory shouldnt affect modern systems that much, but it's unclear for now so I just put that therr.
…30911) Clarify wording in Whats new for Tail call
Pointed out by @smarr that the old wording was confusing.