Ignore:
Timestamp:
Jun 7, 2020, 12:28:06 PM (18 months ago)
Author:
Peter A. Buhr <pabuhr@…>
Branches:
arm-eh, jacob/cs343-translation, master, new-ast, new-ast-unique-expr
Children:
ee06db5c
Parents:
393d59a
Message:

update referee response

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/papers/concurrency/response2

    r393d59a rb54118a  
    692692choosing between a generator or coroutine; either form can receive (input) or
    693693return (output) millions of values. As well, simple versus complex computations
    694 is also not a criterion for selection as both forms can be very
    695 sophisticated. As stated in the paper, a coroutine brings generality to the
    696 implementation because of the addition stack, whereas generators have
    697 restrictions on standard software-engining practices: variable placement, no
    698 helper functions without creating an explicit generator stack, and no symmetric
    699 control-flow.
     694is also not an absolute criterion for selection as both forms can be simple or
     695complex.
     696
     697As stated in the paper, a coroutine brings generality to the implementation
     698because of the addition stack, whereas generators have restrictions on standard
     699software-engineering practices: variable placement, no helper functions without
     700creating an explicit generator stack, and no symmetric control-flow.  It is
     701true that simple generators probably suffer less from restrictions. Also,
     702simplicity means the amount of work done is small so the cost of the
     703suspend/resume becomes a factor, where experiments show suspend/resume for a
     704generator is 10 times faster than for a coroutines.
     705
    700706
    701707    * prefer threads for cases where parallel execution is desired or needed.
Note: See TracChangeset for help on using the changeset viewer.