Hiding internal modules

[andrewray]

Is there an appropriate way to hide a module that is used within a library, but shouldn't be exposed?

[ghost]

If you don't use (wrapped false), then you can simply write a module with the name of the library and expose exactly what you want. Otherwise no.

I don't mind having an option to not install the .cmi for some specific modules. Currently jbuilder works the same whether things are installed or not, so this would need a bit of work to support properly. There would be something to do for wrapped libraries without an explicit interface as well, so that module aliases for these are not exposed externally.

In the meantime I suggest to simply use names that makes it clear that these modules are private.

[rgrinberg]

@andrewray how come you closed this ticket? I think it's a reasonable request, if not a high priority.

[andrewray]

@diml can decide if it should be open or not.

I find the wrapped by default argument, in general, convincing.

For the specific case of lwt, I wonder if we could do an install hack that just removed the offending cmis from lwt_unix.install. Or maybe just rename the modules to something crazy (XXX_internal_dont_use_XXX).

[bobot]

#106 should do what you need. It's part of the features I need for using Jbuilder with Frama-C but I don't want to create too many MR at once.