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: 7290 Reporter:@gasche Assigned to:@gasche Status: resolved (set by @gasche on 2016-07-29T05:13:07Z) Resolution: fixed Priority: normal Severity: minor Target version: 4.04.0 +dev / +beta1 / +beta2 Fixed in version: 4.04.0 +dev / +beta1 / +beta2 Category: ocamldoc Has duplicate:#7410 Monitored by:@hcarty
Bug description
ocamldoc has not been updated to support inline record. This led to a manual build failure that has been fixed by octachron in #690 , but there probably still exists programs on which ocamldoc will fail with an assert failure.
octachron expressed interest in working on this.
I'm setting the target to 4.04+dev because having ocamldoc fail on existing language features may bite users down the road, so fixing this as soon as possible is preferable.
The text was updated successfully, but these errors were encountered:
Expressed interest might be a tad too strong, but anyway here is a pull
request which at least fixes the remaining ocamldoc crashes and adds some basic support for documentation comments within inline records:
Original bug ID: 7290
Reporter: @gasche
Assigned to: @gasche
Status: resolved (set by @gasche on 2016-07-29T05:13:07Z)
Resolution: fixed
Priority: normal
Severity: minor
Target version: 4.04.0 +dev / +beta1 / +beta2
Fixed in version: 4.04.0 +dev / +beta1 / +beta2
Category: ocamldoc
Has duplicate: #7410
Monitored by: @hcarty
Bug description
ocamldoc has not been updated to support inline record. This led to a manual build failure that has been fixed by octachron in #690 , but there probably still exists programs on which ocamldoc will fail with an assert failure.
octachron expressed interest in working on this.
I'm setting the target to 4.04+dev because having ocamldoc fail on existing language features may bite users down the road, so fixing this as soon as possible is preferable.
The text was updated successfully, but these errors were encountered: