export System.Posix.Directory.Common

[JohnLato]

Without DirStream, if you wish to do a deep traversal of a directory structure, it's necessary to stat everything in order to determine if it's a sub-directory (and needs to be descended into) or a regular file. This imposes a significant performance penalty (see https://github.com/JohnLato/posix-paths for benchmarks).

I don't think there's any reason this module can't be exported in its entirety.

[hvr]

Are you actually asking to export the constructor of DirStream?

[JohnLato]

Yes, and probably CDir and CDirent also. I think the most pragmatic way of doing so is exporting this module in its entirety, because I could imagine that someone may want to use one of the FFI calls as well.

[hvr]

@JohnLato But is .Common the proper name for it? It seems more like an .Internal module as we don't want to have to adhere to the PVP for the internal representation (I guess)...

[JohnLato]

Sure, a .Internal name makes sense. Or possibly .Foreign since it's the
lowest level wrapper.

On 02:04, Sun, Dec 7, 2014 Herbert Valerio Riedel notifications@github.com
wrote:

@JohnLato https://github.com/JohnLato But is .Common the proper name
for it? It seems more like an .Internal module as we don't want to have
to adhere to the PVP for the internal representation (I guess)...

—
Reply to this email directly or view it on GitHub
#25 (comment).