issue-3876b0504aff1a6ef28b9d801d0f1303299bea2d.yaml

--- !ditz.rubyforge.org,2008-03-06/issue 
title: document that tailcalls interfere with some mechanisms
desc: ""
type: :task
component: duk
release: v0.11
reporter: sva <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2014-03-15 23:34:54.827025 Z
references: []

id: 3876b0504aff1a6ef28b9d801d0f1303299bea2d
log_events: 
- - 2014-03-15 23:34:54.962918 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-03-17 21:22:08.533628 Z
  - sva <sami.vaarala@iki.fi>
  - commented
  - |-
    Logger name automatic detection would suffer from tail calls.  However,
    because logger creation uses a constructor call there is no problem:
    constructor calls currently block tail call handling.
    
    Similarly, the 'caller' non-standard property would not work properly
    with tail calls.  But that feature disables tail calls altogether now,
    so this problem won't be triggered.
    
    So, at the moment there are no known issues to document.
- - 2014-06-09 10:13:44.896261 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""