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: 5073 Reporter:@alainfrisch Assigned to:@garrigue Status: closed (set by @garrigue on 2012-06-20T10:05:28Z) Resolution: fixed Priority: normal Severity: minor Fixed in version: 4.00.0+dev Category: typing Monitored by:@hcarty@alainfrisch
Bug description
In a record literal expression, an unbound record field error is located on the field expression, not on the label.
E.g.:
{x = 1};;
^
Error: Unbound record field label x
For pattern records, the whole pattern is highlighted. In a sense, the behavior for expressions is better (more precisely localized), but quite misleading.
The location for the faulty identifier itself is not kept in the parse tree. Maybe one should add it?
Original bug ID: 5073
Reporter: @alainfrisch
Assigned to: @garrigue
Status: closed (set by @garrigue on 2012-06-20T10:05:28Z)
Resolution: fixed
Priority: normal
Severity: minor
Fixed in version: 4.00.0+dev
Category: typing
Monitored by: @hcarty @alainfrisch
Bug description
In a record literal expression, an unbound record field error is located on the field expression, not on the label.
E.g.:
{x = 1};;
Error: Unbound record field label x
For pattern records, the whole pattern is highlighted. In a sense, the behavior for expressions is better (more precisely localized), but quite misleading.
The location for the faulty identifier itself is not kept in the parse tree. Maybe one should add it?
Alain
File attachments
The text was updated successfully, but these errors were encountered: