Long chains of aliases cause the compile step to be very memory/space intensive
for a set of files like:
- m1.ml
module Foo = struct
type t
end
- m2.ml
module Previous = M1
module Foo = Previous.Foo
- m3.ml
module Previous = M2
module Foo = Previous.Foo
the generated odoc files (after compilation) get large very quickly:
-r--r--r-- 1 jon staff 428 17 Jun 11:19 foo__M1.odoc
-r--r--r-- 1 jon staff 702 17 Jun 11:19 foo__M2.odoc
-r--r--r-- 1 jon staff 993 17 Jun 11:19 foo__M3.odoc
-r--r--r-- 1 jon staff 1362 17 Jun 11:19 foo__M4.odoc
-r--r--r-- 1 jon staff 1811 17 Jun 11:19 foo__M5.odoc
-r--r--r-- 1 jon staff 2353 17 Jun 11:19 foo__M6.odoc
-r--r--r-- 1 jon staff 2969 17 Jun 11:19 foo__M7.odoc
-r--r--r-- 1 jon staff 3692 17 Jun 11:19 foo__M8.odoc
-r--r--r-- 1 jon staff 4501 17 Jun 11:19 foo__M9.odoc
-r--r--r-- 1 jon staff 5396 17 Jun 11:19 foo__M10.odoc
-r--r--r-- 1 jon staff 6376 17 Jun 11:19 foo__M11.odoc
-r--r--r-- 1 jon staff 7439 17 Jun 11:19 foo__M12.odoc
-r--r--r-- 1 jon staff 8585 17 Jun 11:19 foo__M13.odoc
-r--r--r-- 1 jon staff 9816 17 Jun 11:19 foo__M14.odoc
-r--r--r-- 1 jon staff 11131 17 Jun 11:19 foo__M15.odoc
-r--r--r-- 1 jon staff 12532 17 Jun 11:19 foo__M16.odoc
-r--r--r-- 1 jon staff 14018 17 Jun 11:19 foo__M17.odoc
-r--r--r-- 1 jon staff 15585 17 Jun 11:19 foo__M18.odoc
-r--r--r-- 1 jon staff 17231 17 Jun 11:19 foo__M19.odoc
-r--r--r-- 1 jon staff 18961 17 Jun 11:19 foo__M20.odoc
-r--r--r-- 1 jon staff 20775 17 Jun 11:19 foo__M21.odoc
-r--r--r-- 1 jon staff 22673 17 Jun 11:19 foo__M22.odoc
-r--r--r-- 1 jon staff 24655 17 Jun 11:19 foo__M23.odoc
-r--r--r-- 1 jon staff 26721 17 Jun 11:19 foo__M24.odoc
-r--r--r-- 1 jon staff 28871 17 Jun 11:19 foo__M25.odoc
-r--r--r-- 1 jon staff 31105 17 Jun 11:19 foo__M26.odoc
-r--r--r-- 1 jon staff 33423 17 Jun 11:19 foo__M27.odoc
-r--r--r-- 1 jon staff 35825 17 Jun 11:19 foo__M28.odoc
-r--r--r-- 1 jon staff 38311 17 Jun 11:19 foo__M29.odoc
-r--r--r-- 1 jon staff 40881 17 Jun 11:19 foo__M30.odoc
-r--r--r-- 1 jon staff 43535 17 Jun 11:19 foo__M31.odoc
-r--r--r-- 1 jon staff 46273 17 Jun 11:19 foo__M32.odoc
-r--r--r-- 1 jon staff 49095 17 Jun 11:19 foo__M33.odoc
-r--r--r-- 1 jon staff 52001 17 Jun 11:19 foo__M34.odoc
-r--r--r-- 1 jon staff 54991 17 Jun 11:19 foo__M35.odoc
-r--r--r-- 1 jon staff 58065 17 Jun 11:19 foo__M36.odoc
-r--r--r-- 1 jon staff 61223 17 Jun 11:19 foo__M37.odoc
-r--r--r-- 1 jon staff 64465 17 Jun 11:19 foo__M38.odoc
-r--r--r-- 1 jon staff 67791 17 Jun 11:19 foo__M39.odoc
-r--r--r-- 1 jon staff 71201 17 Jun 11:19 foo__M40.odoc
-r--r--r-- 1 jon staff 74695 17 Jun 11:19 foo__M41.odoc
-r--r--r-- 1 jon staff 78273 17 Jun 11:19 foo__M42.odoc
-r--r--r-- 1 jon staff 81935 17 Jun 11:19 foo__M43.odoc
-r--r--r-- 1 jon staff 85681 17 Jun 11:19 foo__M44.odoc
-r--r--r-- 1 jon staff 89511 17 Jun 11:19 foo__M45.odoc
-r--r--r-- 1 jon staff 93425 17 Jun 11:19 foo__M46.odoc
-r--r--r-- 1 jon staff 97423 17 Jun 11:19 foo__M47.odoc
-r--r--r-- 1 jon staff 101505 17 Jun 11:19 foo__M48.odoc
-r--r--r-- 1 jon staff 105671 17 Jun 11:19 foo__M49.odoc
-r--r--r-- 1 jon staff 109921 17 Jun 11:19 foo__M50.odoc
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. The main purpose of this is to keep the issue tracker focused to what is actively being worked on, so that the amount and variety of open yet inactive issues does not overwhelm contributors.
An issue closed as stale is not rejected — further discussion is welcome in its closed state, and it can be resurrected at any time. odoc maintainers regularly check issues that were closed as stale in the past, to see if the time is right to reopen and work on them again. PRs addressing issues closed as stale are as welcome as PRs for open issues. They will be given the same review attention, and any other help.