@alexmiller This is the reason of the general sensation of the opaque development process of clojure, tickets closed without any explanation, and many other similar stories. A simple rationale and little discussion would be helpful for the both sides... but the current approach only makes damage to the community and removes all desire to contribute...

IMHO

noted

a question, don't want to rush, is the core.async version with the fix for the below warning about to be released by any chance? WARNING: bounded-count already refers to: #'clojure.core/bounded-count in namespace: clojure.core.async, being replaced by: #'clojure.core.async/bounded-count

should be released as of a few weeks ago

(I’m already using it in prod)

@jr thanks, I spoke without checking...shame on me 😄

This is really a minor thing but I believe the positional constructors defined for defrecords and deftypes could be type hinted (with the actual class name), see https://github.com/clojure/clojure/blob/clojure-1.8.0/src/clj/clojure/core_deftype.clj#L251.

to what end? everything is an Object field in the record or type anyways (other than ^long and ^double hinted primitive fields)

it would hint the return value with the classname, not the arguments. see my snippet

maybe String wasn't the best class to use in this case, I should have used a record

I've updated my snippet