Project

Profile

Help

Bug #2233

closed

Poor diagnostics on type error with higher-order function

Added by Michael Kay about 10 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Diagnostics
Sprint/Milestone:
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.

Actions #1

Updated by Michael Kay about 10 years ago

  • Status changed from In Progress to Resolved

A patch has been committed on the 9.6 and 9.7 branches

Actions #2

Updated by O'Neil Delpratt almost 10 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in version set to 9.6.0.3

Bug fix patch applied to the Saxon 9.6.0.3 maintenance release

Actions #3

Updated by O'Neil Delpratt almost 9 years ago

  • Sprint/Milestone set to 9.6.0.3
  • Applies to branch 9.6 added
  • Fix Committed on Branch 9.6 added
  • Fixed in Maintenance Release 9.6.0.3 added

Please register to edit this issue

Also available in: Atom PDF