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
When programming with objects (but I suppose the same thing would apply to
modules), the error messages can be hard to read (e.g. when a 'class type dec
does not match' error stretches out over a few screens). Would you consider
printing out ellipses for the parts which match and then only text for the parts
which don't? Thanks - Ethan
Also, since I have the ear of an official caml rider, is there any plan to
implement type-slicing or guarded recursive data types?
The text was updated successfully, but these errors were encountered:
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 3437
Reporter: administrator
Status: acknowledged
Resolution: open
Priority: normal
Severity: feature
Category: typing
Bug description
Full_Name: Ethan Aubin
Version: 3.08.1
OS: XP
Submission from: h000393e64fbb.ne.client2.attbi.com (65.96.37.11)
When programming with objects (but I suppose the same thing would apply to
modules), the error messages can be hard to read (e.g. when a 'class type dec
does not match' error stretches out over a few screens). Would you consider
printing out ellipses for the parts which match and then only text for the parts
which don't? Thanks - Ethan
Also, since I have the ear of an official caml rider, is there any plan to
implement type-slicing or guarded recursive data types?
The text was updated successfully, but these errors were encountered: