3 ms·

Thanks so much for the detailed example. Bookmarking for when I need to find it again...

• steveklabnik 1y ago
  No problem! I also left this response to someone on reddit who said similar: Nice. I want to write about my experiences someday, but some quick random thoughts about this: My repository files are huge. i need to break them up. More submodules can work, and defining the inherent methods in a different module than the trait implementation. I've found the directory structure this advocates, that is, ├── src │ ├── domain │ ├── inbound │ ├── outbound gets a bit weird when you're splitting things up by feature, because you end up re-doing the same directories inside of all three of the submodules. I want to see if moving to something more like ├── src │ ├── feature1 │ │ ├── domain │ │ ├── inbound │ │ ├── outbound │ ├── feature2 │ │ ├── domain │ │ ├── inbound │ │ ├── outbound feels better. Which is of course its own kind of repetition, but I feel like if I'm splitting by feature, having each feature in its own directory with the repetition being the domain/inbound/outbound layer making more sense. I'm also curious about if coherence will allow me to move this to each feature being its own crate. compile times aren't terrible right now, but as things grow... we'll see.