Tatu Saloranta

I cannot comment a lot on changes, but I like the idea -- one thing that I was always trying to suggest was that as much work as possible SHOULD...

Ok good improvements! And pretty impressive performance gains @k163377 couple of general notes/answers: * Yes, it's fine to keep this against 2.12 before we merge, just change it before merge...

One comment/thought inspired by changes here, @dinomite and @k163377 -- now that there are quite a few boolean-valued configuration settings, I wonder if these should grouped as something like `KotlinMapper.Feature`?...

I suspect this could be related to the perennial "1-argument constructors are ambiguous" problem? Although with NamingStrategy there is also the possibility of problems (from databind) wrt too-late binding of...

I'd probably recommend not adding too many new mutator methods on `ObjectMapper` since that approach will disappear with Jackson 3.0 (... in due time), and instead of that add to...

Yeah that's fine, it'd be for Kotlin module maintainers (@dinomite ) to review and approve.

Please do not use `master` as that is for 3.0.0 (and still has couple of issues) -- code for 2.10 is in `2.10` branch (for patches to 2.10), and `2.11`...

Unfortunately there the maintainers of this module appear to be currently busy with other projects, help wanted and so on. :-/ You may want to reach out on `jackson-dev` mailing...

@hartmut-co-uk Name resolution occurs within `jackson-databind`, based on information it collects, with help of Kotlin module. Key pieces are: 1. `AnnotationIntrospector` (and its databind impl, `JacksonAnnotationIntrospector`, and Kotlin override(s) via...

Ok, so, there is one thing that is added for Jackson 2.11, to be released soon (as soon as we get #281 handled to some degree), that could help improve...