jwilm

7 ms·

61.
by jwilm 10y ago
> How has it helped? Does it just keep the code clean or has it found mistakes and stuff like that too? Clippy hasn't found any bugs in our code that I'm aware of, but it has been invaluable even so. Clippy is really good at pr
62.
by jwilm 10y ago
Thank you for the compliments! I'm especially glad you like the diagram.
63.
by jwilm 10y ago
I'm still a bit hesitant to pick up tokio and tokio-hyper so soon. We've got a lot of production miles on the current async client - on the order of billions of HTTP requests. Qualifying the new hyper code for production use will
64.
by jwilm 10y ago
We're definitely looking forward to the tokio-based version of Hyper async. In case it wasn't clear from the post, we are actually using the unreleased async version of Hyper (powered by mio/rotor) today.
65.
by jwilm 11y ago
We're around to answer questions! Also, please see the discussion on reddit: https://www.reddit.com/r/rust/comments/4be9lq/onesignal_usin...
66.
Show HN: Rust support in YouCompleteMe(blog.jwilm.io)
4 points by jwilm 11y ago|0 comments
67.
by jwilm 11y ago
> Most notable is a much requested feature from our Android NDK & game developers: code editing and debugging for C/C++ code Does this mean gdb integration with android studio? That would be fantastic! Working with the NDK has b
68.
by jwilm 11y ago
They handle it fine by tracking references at runtime. The advantage here is compile time verification that the reference will stay valid for the life of the struct - zero runtime overhead.