On Thu, Jan 15, 2015 at 4:54 PM, Kevin Wolf wrote:
> Hm, I guess there might be uses for holding references after the
> coroutine has exited if there are external references to the coroutine,
> but is it useful not to drop one reference after the coroutine exits? I
> guess in most cases, and in qe
Am 09.01.2015 um 18:19 hat Marc-André Lureau geschrieben:
> Learn to use the GCoroutine library instead of qemu own coroutine
> implementation.
>
> GCoroutine is hosted on github:
> https://github.com/elmarco/gcoroutine
>
> This allows to share the same coroutine implementation between various
>
On Fri, Jan 09, 2015 at 06:19:50PM +0100, Marc-André Lureau wrote:
> Learn to use the GCoroutine library instead of qemu own coroutine
> implementation.
>
> GCoroutine is hosted on github:
> https://github.com/elmarco/gcoroutine
>
> This allows to share the same coroutine implementation between v
On Fri, Jan 09, 2015 at 05:32:14PM +, Peter Maydell wrote:
> On 9 January 2015 at 17:19, Marc-André Lureau
> wrote:
> > Learn to use the GCoroutine library instead of qemu own coroutine
> > implementation.
> >
> > GCoroutine is hosted on github:
> > https://github.com/elmarco/gcoroutine
> >
>
On 9 January 2015 at 17:19, Marc-André Lureau
wrote:
> Learn to use the GCoroutine library instead of qemu own coroutine
> implementation.
>
> GCoroutine is hosted on github:
> https://github.com/elmarco/gcoroutine
>
> This allows to share the same coroutine implementation between various
> projec
Learn to use the GCoroutine library instead of qemu own coroutine
implementation.
GCoroutine is hosted on github:
https://github.com/elmarco/gcoroutine
This allows to share the same coroutine implementation between various
projects (gtk-vnc and spice-gtk). It is related to the effort to push
coro
