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: 295 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Bug description
Dear Manuel,
Thanks for the beta-testing!
The file byterun/makefile.nt needs to be fixed by adding backtrace.obj to
the OBJ list.
Oups, sorry. I've fixed this.
Compiling our Vault compiler with the new version, I noticed that
camldepend seems to be less smart about local modules with the same name as
some global module. E.g., I had a module env.ml containing a functor called
ENV(...).
Camldepend generated a self-dependency on env.cmo.
More seriously, I'm getting a type error where I did not used to get one.
It seems that Ocaml considers some types to be distinct where they were not
before, although I'm confused as to why. Here's the error.
File "typing/typematch.ml", line 1778, characters 4-19:
This pattern matches values of type Types.presence * ([< Absent] as 'a) but is here used to match values of type Types.presence * Types.presence Type 'a is not compatible with type Types.presence = [ Present of Types.state * Types.type_expr | `Absent]
If I understand it correctly, the compiler complains that `Absent does not
match Types.presence, whereas it should. The error was generated in a
pattern match of the form:
More seriously, I'm getting a type error where I did not used to get one.
It seems that Ocaml considers some types to be distinct where they were not
before, although I'm confused as to why. Here's the error.
I'm a bit surprised that this worked at all before, because I do not
remember any major change there, and multiple matching of variants
with wild patterns on both sides was rather imprevisible.
But anyway this has just been corrected as a side-effect of a bigger
change on how to use exhaustivity information from the match compiler
in typing (namely, do not discard tags explicitely matched from the
synthesized type), to get more previsibility.
Yet, this issue is still in discussion, and the semantics of _ might
change, so mark this code as fragile, as it might need to be adapted
in the future. And inform us if anything strange happens.
Original bug ID: 295
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Dear Manuel,
Thanks for the beta-testing!
Oups, sorry. I've fixed this.
We will look into this.
Cheers,
The text was updated successfully, but these errors were encountered: