Completely unrelated rant. Before Rust really takes off, can someone please, pretty please, for the love of "Bob" and all that is marginally donut-shaped, can s

Completely unrelated rant. Before Rust really takes off, can someone please, pretty please, for the love of "Bob" and all that is marginally donut-shaped, can somebody pleeeeeease tell the Rust community to adopt inheritance-focused hierarchical package naming conventions??? Way back in the day, in like, 1995, there was this thing called Perl. Perl was awesome. You'd think, "I want to make a custom LDAP client". And you'd look in CPAN for an LDAP module, and it'd be there (https://metacpan.org/pod/Net::LDAP https://metacpan.org/pod/Net::LDAP), and you'd use it. A while later you realize you want to manipulate Active Directory SIDs. So you create a new module that inherits Net::LDAP, and publish it (https://metacpan.org/pod/Net::LDAP::SID https://metacpan.org/pod/Net::LDAP::SID). On the plus side: everyone can install your module to get extra functionality with their existing code; people don't need to reinvent the wheel completely to do something a little different; and it's easy to see which module provides what/inherits from what. On the down side: boring names for modules. (is that a downside?)