Ticket #215 (new defect)

Opened 1 year ago

Last modified 1 month ago

(Resolved) Language: Minimum requirements for proper tail calls

Reported by: lth Assigned to: anonymous
Type: defect Priority: major
Milestone: Component: Spec
Version: Harmony Keywords:
Cc: brendan, graydon, jeffdyer, chrispi, dherman, david-sarah@jacaranda.org

Description

The proper tail calls proposal http://wiki.ecmascript.org/doku.php?id=proposals:proper_tail_calls now includes a set of minimum requirements on conforming implementations. This set balances the possibilities for static analysis (in ahead-of-time implementations) with the difficulties of same (in small on-line implementations).

We can try to expand the set of situations in which proper tail calls are possible, and we should check that the list in the proposal is actually valid.

If the number of situations in which proper tail calls are possible is too low, then we should consider deferring the proposal.

Attachments

Change History

Changed 1 year ago by lth

  • owner deleted
  • component changed from Proposals to Spec

We believe this.

Changed 1 year ago by lth

  • priority changed from major to trivial
  • summary changed from Minimum requirements for proper tail calls to (Resolved) Language: Minimum requirements for proper tail calls

Changed 1 month ago by David-Sarah Hopwood

  • cc changed from brendan,graydon,jeffdyer,chrispi,dherman to brendan, graydon, jeffdyer, chrispi, dherman, david-sarah@jacaranda.org
  • priority changed from trivial to major
  • version changed from 4 to Harmony

Proposal still relevant to ES-Harmony (maybe even ES3.1 if we can spec it in time).

Changed 1 month ago by brendan

No, ES3.1 is not going to take on more substantive additional work. This was made clear by John Neumann, TC39 Chair, at the Kona meeting.

/be

Note: See TracTickets for help on using tickets.