asonix

Has there been any movement on this? I was looking into this and it seems like https://gitlab.gnome.org/GNOME/vala/-/merge_requests/133 is no longer an issue, but gir still does not properly generate bindings...

Additional info: This occurs frequently for me, since I have multiple workspaces open and switch between them frequently while a chat application is generating notifications frequently. It seems to happen...

I'm also wondering if there is a specific reason that actix-codec is distinct from tokio-util::codec

If that repo is the main one now, the cargo.toml should be updated to point to it

https://git.asonix.dog/asonix/mmo-rust-server Here's how I'd do it

Go for it! I've been playing a lot with Tokio for various projects of mine, and this is the cleanest I've been able to come up with for doing asynchronous...

oh also, there's part of your code that does ```rust match true { true => Ok(Loop::Continue()) false => Ok(Loop::Break()) } ``` but you could do ```rust Ok(Loop::Continue()) ``` and it...

Here's the really interesting thing, though. Using artillery with your config, I'm getting opposite results from what you've shown. I'm wondering if this is an OS or CPU (or both)...

In related news, tokio just merged some synchronization primatives: https://github.com/tokio-rs/tokio/pull/839 This means that using mpsc and oneshot channels should be faster (if the tokio versions are used over the futures...

I'm going to be honest, I don't know enough about benchmarking and artillery to understand what adding more thinks does. The docs say "To pause the virtual user for N...