Hello, as far as I can tell, it is a requirement that a module names matches its file name, which means that one cannot split a module into several files, correct? I'm curious about the rational behind it? Is it "just" so that the compiler has an easier time resolving imports or are there other reasons as well?
One could argue that it forces users to keep things that belong together logically also physically together and that it encourages you to keep modules small. On the other hand, message communication between modules seems to be a bit unwieldy which makes me hesitant to create too big of a module hierarchy. From a beginner's point of view, I like the idea of "partial module" declarations, but I can imagine that there are good reasons against that. best, Robert -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
