wrongwrong

`kotlin.time.Duration` is a `value class`. As shown in #199, `jackson-module-kotlin` does not currently support deserialization of functions that call `value class` as an argument.

The `kotlinx-metadata-jvm` only provides the ability to read information from `Metadata` annotations. The rest of the processing will be done via `Java Reflection`. This means that only the `Kotlin` module...

> this would reduce the amount of reflection required when dealing with Kotlin objects? I don't have a clear comparison, but it probably is. I think the explanation of `moshi-metadata-reflect`...

> Main question would just be how likely this would be to cause issues; would there be enough time to prove safety of the new approach for, say, 2.13 I...

@dinomite @cowtowncoder As a preliminary step to working on this change, I am planning to do some refactoring regarding readability and performance. I apologize for the many reviews I have...

I also have a question about the behavior when defining multiple `JsonCreators`. As shown in the following test, when I define a `JsonCreator` in both `Constructor` and `Factory`, no error...

@cowtowncoder Could you please take a look at this question?

@dinomite Fixing this issue will be easier if #510 can be merged. I would appreciate it if you could review it if possible.

@dinomite I created a refactored branch of the argument reading process that is a follow-up to this PR. Without default arguments, the performance appears to be better than #439 (i.e.,...

@cowtowncoder Thanks for the reply. > One thing that would be nice, but I am not sure if it is possible, would be to have choice of two backends for...