-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Description
A great package, I'm enjoying it thoroughly, with the exception of compile errors.
It quite often happens the type checker substitutes the type alias for the actual type (espcially in the case of an inferred type and especially in the case of an error) and produces errors more difficult to parse than they would be if the lens was stored not as a tuple but rather a record:
expected: Lens<MyRecord, int>
vs
expected: (MyRecord -> int) * (int -> MyRecord -> MyRecord)Which needless to say gets worse with the complication of either of the types involved.
Would this be something you'd be willing to consider changing or is it too compatibility breaking to be worth thinking about?
Metadata
Metadata
Assignees
Labels
No labels