You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5641 Reporter:@zoggy Status: resolved (set by @xavierleroy on 2012-06-17T08:25:38Z) Resolution: suspended Priority: normal Severity: minor Version: 4.00.0+beta2/+rc1 Category: configure and build/install Monitored by: mww @glondu@hcarty
Bug description
It would be useful and convenient to install the .mli of the modules being installed in compiler-libs.
The text was updated successfully, but these errors were encountered:
IMO, the goal of installing compiler-libs is to allow end-users to compile third-party packages that depend on those compiler modules (for instance, some code base analysis tools). Developers of such tools could use .mli files as documentation (technically, they don't need them to compile their work), but one could argue that the .mli files of the compiler don't contain a lot of information, and that developers would actually like to have access to the implementation as well. And I think this is fine: developers of low-level tools, strongly tied to the compiler, will download the source code as a reference.
But if the demand is strong enough, I'm not opposed to installing .mli files.
I agree with Alain Frisch's comment. The .mli of the compiler are not (by a long shot) written in a way that would document the compiler internals. I don't see added value in installing them.
Original bug ID: 5641
Reporter: @zoggy
Status: resolved (set by @xavierleroy on 2012-06-17T08:25:38Z)
Resolution: suspended
Priority: normal
Severity: minor
Version: 4.00.0+beta2/+rc1
Category: configure and build/install
Monitored by: mww @glondu @hcarty
Bug description
It would be useful and convenient to install the .mli of the modules being installed in compiler-libs.
The text was updated successfully, but these errors were encountered: