Actions
Bug #2233
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Poor diagnostics on type error with higher-order function
Start date:
2014-11-21
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.6
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:
Platforms:
Description
Given a higher-order function call such as
filter((1 to 5), upper-case#1)
which generates a type error because upper-case() expects a string rather than an integer, the diagnostics incorrectly state that the expected type of the second argument of filter() is xs:string.
Please register to edit this issue
Actions