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: 5843 Reporter: jpdeplaix Assigned to:@zoggy Status: assigned (set by jpdeplaix on 2012-12-04T22:31:23Z) Resolution: open Priority: normal Severity: minor Version: 4.00.0 Target version: later Category: ocamldoc Related to:#3947
Bug description
I'm trying to include a functor application when the functor is defined in the same module (otherwise it seems to work) and ocamldoc warns with:
This is due to the fact that ocamldoc does not support environments. Here the include requires to access the environment to be able to know the origin of the included module type.
This is a long-time missing analysis in ocamldoc, requiring quite a lot of work.
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
For the record, this will be fixed comprehensively in odoc when ocaml/odoc#439 is merged and released. All functor applications should render correctly in the new model present in that PR.
Original bug ID: 5843
Reporter: jpdeplaix
Assigned to: @zoggy
Status: assigned (set by jpdeplaix on 2012-12-04T22:31:23Z)
Resolution: open
Priority: normal
Severity: minor
Version: 4.00.0
Target version: later
Category: ocamldoc
Related to: #3947
Bug description
I'm trying to include a functor application when the functor is defined in the same module (otherwise it seems to work) and ocamldoc warns with:
Warning: Module or module type ?? not found
I've attached a test-case.
Steps to reproduce
ocamldoc -html ocamldoc.mli
File attachments
The text was updated successfully, but these errors were encountered: