Closed agarwal closed 8 years ago
I've crossed out the first request here. I already have some need for the Path
module in a pure
library of another project. Nonetheless, we can still include
modules to create a final monolithic API.
well, good thing I had not started it yet ;o)
2015-10-27 21:26 GMT+01:00 Ashish Agarwal notifications@github.com:
I've crossed out the first request here. I already have some need for the Path module in a pure library of another project. Nonetheless, we can still include modules to create a final monolithic API.
— Reply to this email directly or view it on GitHub https://github.com/solvuu/phat/issues/10#issuecomment-151633836.
Done in 4719dd4c7efd6b5e0ed4ac7a51d1a74ef765052c.
In contrast to most of our projects, this one will be easiest to use with all types and functions under a single module. Concretely, we should:
[ ] mergeThe separation is an unnecessary annoyance for now, but could be reintroduced later if any users needed to avoid thepure
library toasync-unix
.async
dependency.Either put all code directly into a singledophat.ml/i
file, orinclude Path
andinclude Filesys
. Don't worry about the fact that our build system will forcibly name the modulePhat_async_unix.Std
. We'll fix that later. For now, client code can domodule Phat = Phat_async_unix.Std
.