• Jonathan Dunlap (6/6) Jun 11 2013 I was listening to one of the DConf sessions and where was some
• Jonathan Dunlap (2/9) Jun 15 2013
• Sean Kelly (9/17) Jun 17 2013 Fibers don't actually execute asynchronously. They represent an =

"Jonathan Dunlap" <jadit2 gmail.com> writes:

I was listening to one of the DConf sessions and where was some 

future. Recently I learned about D's fibers... and it looks like 
the same thing to me. What are the major differences in principle?

-Jonathan
 jonathanAdunlap

"Jonathan Dunlap" <jadit2 gmail.com> writes:

*bump*

On Tuesday, 11 June 2013 at 19:57:27 UTC, Jonathan Dunlap wrote:
 I was listening to one of the DConf sessions and where was some 

 future. Recently I learned about D's fibers... and it looks 
 like the same thing to me. What are the major differences in 
 principle?

 -Jonathan
  jonathanAdunlap

Sean Kelly <sean invisibleduck.org> writes:

Fibers don't actually execute asynchronously.  They represent an =
alternate execution context (code and stack) but are executed by the =
thread that calls them, and control is returned when they either yield =
or complete.  This video is a good introduction to fibers:

http://vimeo.com/1873969

On Jun 15, 2013, at 10:54 AM, Jonathan Dunlap <jadit2 gmail.com> wrote:

 *bump*
=20
 On Tuesday, 11 June 2013 at 19:57:27 UTC, Jonathan Dunlap wrote:
 I was listening to one of the DConf sessions and where was some talk =



Recently I learned about D's fibers... and it looks like the same thing =
to me. What are the major differences in principle?
=20
 -Jonathan
  jonathanAdunlap

=20