Why is there "No matching ctor" for seemingly unambiguous type-hinted constructor call?

Question

Using Netty from Clojure, the following theoretically unambiguous constructor call fails to resolve, both in Cursive (which incorrectly lists both 3-arity options for disambiguation) and in the REPL (which throws IllegalArgumentException No matching ctor). The un-hinted version also fails in the same way.

(DefaultFullHttpResponse. protocol status ^ByteBuf buffer)

Available constructor signatures are:

• HttpVersion HttpResponseStatus
• HttpVersion HttpResponseStatus ByteBuf ← unambiguously identified by arity + single type hint
• HttpVersion HttpResponseStatus boolean
• HttpVersion HttpResponseStatus boolean boolean
• HttpVersion HttpResponseStatus ByteBuf boolean
• HttpVersion HttpResponseStatus ByteBuf boolean boolean
• HttpVersion HttpResponseStatus ByteBuf HttpHeaders HttpHeaders

Why?

Answer 1

I was able to get this working by "redundantly" hinting the first argument as well:

(DefaultFullHttpResponse. ^HttpVersion protocol status ^ByteBuf buffer)

This was surprising!