Add eager and lazy future support. #114
Conversation
It seems that thread local variables are not updated properly on mac, which might be a [bug](https://llvm.org/bugs/show_bug.cgi?id=23154), filed anyway. Currently, on mac, only one OS thread is used.
|
I get the same tests results on my Mac. I would like to get an overview of the changes with you, since there are many interesting stuff happening in the scheduler. On another note, not really related to this commit: I believe we need to re-think where we are going. We keep breaking stuff in Mac and continue with a "I'll solve it later". If we continue with this approach, our baggage will grow up to a point where we will not be able to support Mac (this is not related to the commit, or you, but to the way we are doing things ever since we moved to the new RT). Let me know when you have some time to give me an overview of your changes. |
|
Good to know. After lunch would be great. As for the mac breaking issues, we could discuss it more in the morning meeting. |
Add eager and lazy future support.
It seems that thread local variables are not updated properly on mac,
which might be a bug,
filed anyway.
Currently, on mac, only one OS thread is used.
Test result on my box (Linux):
Tests passed: 53/58
Tests failed: 5/58
await
deadlock_yourself
parametricClasses
parametricPrint
suspend