Skip to content

Add hint to "Unbound value .{}" error messages #6765

@vicuna

Description

@vicuna

Original bug ID: 6765
Reporter: @alainfrisch
Assigned to: @Octachron
Status: resolved (set by @Octachron on 2017-03-07T13:37:58Z)
Resolution: fixed
Priority: low
Severity: feature
Version: 4.03.0+dev / +beta1
Category: typing
Tags: patch
Monitored by: @gasche @hcarty @dbuenzli

Bug description

Now that bigarray index operators are defined in Bigarray, one needs to explicitly open this module to be able to use these operators (.{}, .{}<-, and -nary forms). To help in the transition, one could add a special case in the "Unbound value" error printer to suggest opening Bigarray when the name of the unbound value is one of the new operators.

Another approach to simplify porting big code bases would be to add a hack in the type-checker to force looking for these operators in Bigarray instead of failing with Unbound value, and issue a "Deprecated" warning when this is needed.

Ref:
#69

File attachments

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions