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: 4871 Reporter: fbesson Status: resolved (set by @damiendoligez on 2012-07-11T12:20:32Z) Resolution: suspended Priority: normal Severity: minor Version: 3.11.0 Category: ~DO NOT USE (was: OCaml general)
Bug description
Hello,
Ocamlyacc handles type scopes differently in the mli and ml.
For instance, suppose I have a file A.ml which defines a type t and a module A.
In B.mly, in the header I "open A" and my start symbol has type A.t
If I write A.t, B.mli compiles but B.ml does not.
If I write t, B.mli does not compile but B.ml would.
Ok, it is probably bad practice to shadow module names.
Yet the current behaviour is a little inconsistent...
Best,
The text was updated successfully, but these errors were encountered:
Original bug ID: 4871
Reporter: fbesson
Status: resolved (set by @damiendoligez on 2012-07-11T12:20:32Z)
Resolution: suspended
Priority: normal
Severity: minor
Version: 3.11.0
Category: ~DO NOT USE (was: OCaml general)
Bug description
Hello,
Ocamlyacc handles type scopes differently in the mli and ml.
For instance, suppose I have a file A.ml which defines a type t and a module A.
In B.mly, in the header I "open A" and my start symbol has type A.t
If I write A.t, B.mli compiles but B.ml does not.
If I write t, B.mli does not compile but B.ml would.
Ok, it is probably bad practice to shadow module names.
Yet the current behaviour is a little inconsistent...
Best,
The text was updated successfully, but these errors were encountered: