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: 6885 Reporter:@gasche Assigned to:@Octachron Status: resolved (set by @Octachron on 2017-02-23T23:49:59Z) Resolution: fixed Priority: normal Severity: text Version: 4.03.0+dev / +beta1 Target version: later Category: documentation Tags: junior_job Related to:#6139
Bug description
The bigarray access syntax is documented as an extension in the manual:
We should explicitly document the fact that, starting at 4.03, "open Bigarray" needs to be used for this syntax to be available for bigarrays. This is one of the breaking changes coming with 4.03.
There are discussions of having a tailored error message, or maybe even supporting the bigarray-syntax with a deprecated backward-compatibility mode for now, but in any case we should document "open Bigarray" as the proper long-term solution.
The text was updated successfully, but these errors were encountered:
Another problem with the current documentation in the manual is that the translation table between the (.{}) operators and the bigarray functions does no longer describe accurately the actual desugaring.
I think it might be better to document first the new syntax for index operators, and then details the specificities of the (.{}) operators family and its link with the bigarray library.
Original bug ID: 6885
Reporter: @gasche
Assigned to: @Octachron
Status: resolved (set by @Octachron on 2017-02-23T23:49:59Z)
Resolution: fixed
Priority: normal
Severity: text
Version: 4.03.0+dev / +beta1
Target version: later
Category: documentation
Tags: junior_job
Related to: #6139
Bug description
The bigarray access syntax is documented as an extension in the manual:
http://caml.inria.fr/pub/docs/manual-ocaml/extn.html#sec240
We should explicitly document the fact that, starting at 4.03, "open Bigarray" needs to be used for this syntax to be available for bigarrays. This is one of the breaking changes coming with 4.03.
There are discussions of having a tailored error message, or maybe even supporting the bigarray-syntax with a deprecated backward-compatibility mode for now, but in any case we should document "open Bigarray" as the proper long-term solution.
The text was updated successfully, but these errors were encountered: