A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-July/046347.html below:

[Python-Dev] Proper tail recursion

[Python-Dev] Proper tail recursion [Python-Dev] Proper tail recursionJeremy Hylton jhylton at gmail.com
Mon Jul 19 18:48:11 CEST 2004
On Mon, 19 Jul 2004 12:27:58 -0400, Chris King <colanderman at gmail.com> wrote:
> Given the proposed changes:
> 
> 1) make a seperate eval loop that supports tail calls so as not to
> impact performance of normal programs,
> 2) force tail calls to be explicitly enabled using a run-time function call,
> 3) print a warning in stack traces when tail calls are enabled and used.
> 
> is Guido still -1 on this?

Just a guess but "make a seperate eval loop" sounds like a sure way to
get a 10,000 pound weight dropped on you? <wink>  Seriously, how do
you accomplish this without code duplication?

Jeremy
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4