I was looking at the current state of the swiftmodule layout in the toolchain. The current layout appears to be:
Linux and Windows:
└─ Toolchains └─ ... └─ usr └─ lib └─ swift └─ [os] └─ [arch] ├─ [module].swiftdoc ├─ [module].swiftinterface └─ [module].swiftmodule
└─ Toolchains └─ ... └─ usr └─ lib └─ swift └─ [os] └─ [module].swiftmodule ├─ [arch].swiftdoc ├─ [arch].swiftinterface └─ [arch].swiftmodule
There is something to be said for the structure in the Darwin case. It actually makes it easier to find the module in the list, it makes it easier to support multiple architectures, and it would make the directory structure uniform across the platforms. It would also allow us to simplify a bit of logic since the compiler would only need a single path.
I was wondering if there is a strong reason to not switch over the Linux (and Windows) platforms to that directory structure.