Skip to content

gh-128563: Clarify clarificatory tail calling wording in What's New #129812

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

Merged
merged 1 commit into from
Feb 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions Doc/whatsnew/3.14.rst
Original file line number Diff line number Diff line change
Expand Up @@ -230,13 +230,15 @@ tested and can validate its improved performance.
For further information on how to build Python, see
:option:`--with-tail-call-interp`.

(Contributed by Ken Jin in :gh:`128718`, with ideas on how to implement this
in CPython by Mark Shannon, Garret Gu, Haoran Xu, and Josh Haberman.)

.. note::

This is not to be confused with tail call optimization of Python code.
Python functions do not currently have tail call optimization.
This is not to be confused with `tail call optimization`__ of Python
functions, which is currently not implemented in CPython.

__ https://en.wikipedia.org/wiki/Tail_call

(Contributed by Ken Jin in :gh:`128718`, with ideas on how to implement this
in CPython by Mark Shannon, Garret Gu, Haoran Xu, and Josh Haberman.)


Other language changes
Expand Down
Loading