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: 3723 Reporter: administrator Assigned to:@damiendoligez Status: resolved (set by @mshinwell on 2016-12-07T17:50:50Z) Resolution: fixed Priority: normal Severity: feature Category: ~DO NOT USE (was: OCaml general)
Hi, I discovered that true/false/()/[] are treated like built-in constant
constructors.
(I accidentally typed 'type u = ()' instead of 'type u = unit'.)
Ocaml allows me to use 3 of these constructors in new type:
type t = true
type f = false
type u = ()
but
type l = []
fails with a parse error. Do people actually reuse these constructors? Maybe
their use on the rhs of a type decl could be deprecated or removed in 3.09?
Cheers - ethan.aubin@pobox.com
The text was updated successfully, but these errors were encountered:
Original bug ID: 3723
Reporter: administrator
Assigned to: @damiendoligez
Status: resolved (set by @mshinwell on 2016-12-07T17:50:50Z)
Resolution: fixed
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Ethan Aubin
Version: 3.07+2 and 3.08.3
OS: solaris/linux
Submission from: c-24-60-21-144.hsd1.ma.comcast.net (24.60.21.144)
Hi, I discovered that true/false/()/[] are treated like built-in constant
constructors.
(I accidentally typed 'type u = ()' instead of 'type u = unit'.)
Ocaml allows me to use 3 of these constructors in new type:
type t = true
type f = false
type u = ()
but
type l = []
fails with a parse error. Do people actually reuse these constructors? Maybe
their use on the rhs of a type decl could be deprecated or removed in 3.09?
Cheers - ethan.aubin@pobox.com
The text was updated successfully, but these errors were encountered: