On 09/25/2014 05:40 AM, Steven Schveighoffer wrote:
> On 9/23/14 7:12 PM, Ali Çehreli wrote:
>
>> Can we get rid of the ResultT template parameter? Tricks with variadic
>> templates, the with statement, etc. come to mind but I could not
>> manage it.
>
> I don't think so.
Me neither. :) This que
On 9/23/14 7:12 PM, Ali Çehreli wrote:
Can we get rid of the ResultT template parameter? Tricks with variadic
templates, the with statement, etc. come to mind but I could not manage it.
I don't think so.
yield just returns control back to another fiber. It's not an entry point.
What you *cou
On Tuesday, 23 September 2014 at 22:09:11 UTC, Ali Çehreli wrote:
I think similar questions were asked by others in different
contexts before.
I played with core.thread.Fibre a little bit. As others have
done a number of times before, I tried to make the following
syntax possible inside fiber
On 09/23/2014 03:28 PM, monarch_dodra wrote:
On Tuesday, 23 September 2014 at 22:09:11 UTC, Ali Çehreli wrote:
So near and yet so far... :)
Ali
You explain "how" you want to achieve your goal, but I'm not sure I
understand "what" the goal is. Perhaps if you explain that in more
detail, I'd ha
On Tuesday, 23 September 2014 at 22:09:11 UTC, Ali Çehreli wrote:
So near and yet so far... :)
Ali
You explain "how" you want to achieve your goal, but I'm not sure
I understand "what" the goal is. Perhaps if you explain that in
more detail, I'd have a better understanding of the problem.
I think similar questions were asked by others in different contexts before.
I played with core.thread.Fibre a little bit. As others have done a
number of times before, I tried to make the following syntax possible
inside fiber code:
yield(42);
I wonder whether there is a clever trick to
