make API a monolithic module

[agarwal]

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:

[ ] merge pure library to async-unix. The separation is an unnecessary annoyance for now, but could be reintroduced later if any users needed to avoid the async dependency.

• Either put all code directly into a single phat.ml/i file, or do include Path and include Filesys. Don't worry about the fact that our build system will forcibly name the module Phat_async_unix.Std. We'll fix that later. For now, client code can do module Phat = Phat_async_unix.Std.

[agarwal]

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.

[pveber]

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
#10 (comment).

[agarwal]

Done in 4719dd4.