Unknown return type class throws NPE instead of useful exception

Description

This is a regression from CLJ-1232 - if you specify a return type class that is not fully-qualified or imported, you now get an NPE instead of a useful error message.

Cause: The new code that resolves classes does not handle the possible null return value of Compiler$HostExpr/maybeClass.

Solution: Check for null and fall back to the original argvecs, which will result in the original message.

Patch: clj-1868.patch

Environment

None

Attachments

1

Activity

Show:

Nicola Mometto December 17, 2015 at 11:10 PM

Dupe of

Completed

Details

Assignee

Reporter

Approval

Ok

Patch

Code and Test

Priority

Affects versions

Fix versions

Created December 17, 2015 at 7:06 PM
Updated January 8, 2016 at 4:04 PM
Resolved January 8, 2016 at 4:04 PM