[HN Gopher] SRFI 226: Control Features
       ___________________________________________________________________
        
       SRFI 226: Control Features
        
       Author : bshanks
       Score  : 19 points
       Date   : 2022-12-09 02:03 UTC (2 days ago)
        
 (HTM) web link (srfi.schemers.org)
 (TXT) w3m dump (srfi.schemers.org)
        
       | LanternLight83 wrote:
       | I read this after perusing the linked resources last time it
       | surfaced, and although I'm no expert, I really like this
       | solution. I'd love to hear from the Scheme implimentors and
       | macro-writers who have actually used call/cc. The control offered
       | over the scope of a continuation, reminding me (model-wise) of a
       | patchset cherry-picked off the head of a git branch, appesrs to
       | soundly address preformance concerns, while the ability to return
       | a value to the continuation's call-site looks like a huge
       | advantage.
        
       | tmtvl wrote:
       | _Finally, promises as defined in this specification can deliver
       | multiple values when forced, an extension too natural to ignore_
       | 
       | Oh yes, excellent, looking forward to playing around with
       | multiple-value lazy streams (srfi-41).
        
       | newaccount2021 wrote:
        
       | convolvatron wrote:
       | "Finally, a primitive (call-in-continuation) is provided that
       | allows calling a procedure in a given continuation instead of
       | just delivering values to it."
       | 
       | can anyone add some language about what this is? I read this and
       | the section on it, and remain deeply confused
        
       ___________________________________________________________________
       (page generated 2022-12-11 23:01 UTC)