Composable modules

[canndrew]

It sounds like the main thing you're after here is generic modules. This has come up a few times before (these are the first two examples I found):

Pre-RFC: module-level generics

Abstract This proposes allowing modules to be generic in order to reduce boilerplate: mod self<Executor: Spawn>; struct Foo { executor: Executor } } impl Foo { // ... } would be equivalent to: struct Foo<Executor: Spawn> { executor: Executor } } impl<Executor: Spawn> Foo<Executor> { // ... } Motivation There are cases when a crate author wants to support several strategies for the crate, but adding the appropriate generic that is repeated everywhere decreases readability. Examples may incl…

Parameterized Modules

##Disclaimer: This is not an RFC. This is not even a proto-RFC. I am merely trying to have a disucssion about a problem I see in organizing code, and would like some commentary on this, as well as an exploration of the possible solution space. Do not criticize this as harshly as you would an RFC. It is not complete. It does not discuss drawbacks. Currently datatypes can be parameterized by types. I am going to make the argument that both datatypes and modules should be able to be parameterized …