Ruma, a Matrix homeserver written in Rust
Slightly off-topic, but, as far as Rust goes, I've completely given up on it after realizing (after much study) that it is unsuitable for event-driven (callback-based) design. In short, its idea of ownership, borrowing and references is incompatible with "lower" objects knowing about their "parents" and invoking callbacks to them.<p>I know there are ways to get around but I don't see any which is sufficiently good for me (e.g. low boilerplate, scalable/composable, no compromise of performance). Some details are in my question on StackOverflow[1].<p>One particular example that C and C++ allow is to have an object "self-destruct" itself in a callback (e.g. after a TCP disconnect, EventLoop callbacks Socket callbacks MyClient which directly destroys MyClient including Socket). Yes it is indeed valid to call a (virtual) function on a class and for that class to proceed to delete itself [2]. This is very nice because it removes need to have special cleanup code all around and/or half-dead states. In Rust, this seems impossible by design (i.e. would need unsafe, and it's unclear if the compiler itself allows it anyway).<p>[1] <a href="http://stackoverflow.com/questions/36952894/event-driven-design-with-callbacks-in-rust" rel="nofollow">http://stackoverflow.com/questions/36952894/event-driven-des...</a><p>[2] <a href="http://stackoverflow.com/questions/3150942/c-delete-this" rel="nofollow">http://stackoverflow.com/questions/3150942/c-delete-this</a>