Confusing error shown when type feature is called with wrong arg count #3341
Labels
enhancement
New feature or request
front end
related to the front end until .fum file is created: call and type resolution, type checking, etc.
The following code declares a type
x
and a type featurex.type.y
with two arguments, but callsy
with three argumentsThe error reported, however, complains about
x
being called with the wrong number of arguments:The text was updated successfully, but these errors were encountered: