[D-runtime] Update request from tango runtime

[Sean Kelly]

The thing is that the switch-in/out stuff really isn't meant to be extended.  A whole bunch of stuff would have to be made public for that to work.  I'm also skeptical that a scheduler needs to be integrated directly into the Thread or Fiber classes.  What's the advantage of this design?

On Apr 24, 2011, at 10:27 AM, SiegeLord wrote:

> Anyone at all? At the very least, could you make the Fiber internals protected instead of private? To the best of my understanding of the core.thread module it is impossible right now to create any fundamentally new thread-like objects because necessary initialization happens in thread_init, which isn't a function that can be extended by user level code. It is also impossible to extend Thread/Fiber directly since everything interesting is private and final.
> 
> -SiegeLord
> 
> On 04/19/2011 12:03 PM, SiegeLord wrote:
>> I don't use the feature myself, but a few parts of Tango do use it
>> (primarily the IO classes). I took a cursory look at how it is used and
>> as best as I can tell, most functions are used. Some unused functions
>> seem to be 'ready' and 'spawn'.
>> 
>> I also looked into make a derived Fiber class with those features, but
>> some functions (e.g. switchOut) are final...
>> 
>> -SiegeLord
>> _______________________________________________
>> D-runtime mailing list
>> D-runtime at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/d-runtime
> _______________________________________________
> D-runtime mailing list
> D-runtime at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/d-runtime