Jake Wharton

Performance is not a concern. The serialization model is only built once. It's more that the magical behavior is needless and you should embrace the naming conventions of the layer...

Minifying names automatically is horrifying. It's impossible to make deterministic such that you retain compatibility across compilations and deployments. Persistence or blue/green deployment is thus impossible. I'm happy to fight...

The only duplicate code is where you've specified a `@SerialName` where one isn't needed. Otherwise you're clearly mapping across domains in which case you are required to specify the identifier...

> not addressing our question I'm not the library author so I cannot answer the question. I can merely argue against this feature's inclusion as strongly as I can having...

I don't think it's supported yet, but you can annotate packages with Checker Framework's `@DefaultQualifier` annotation to make the default nullable.

In practice this will be the exact same thing as the generic parameter will be widened to `Any`. For example, `combineLatest(listOf(just(1), just("hey")), values -> /* it's Array here */)`. Reification...

More lightweight how? On Sat, Apr 29, 2017, 8:25 AM Stepan Goncharov wrote: > I prefer rxKonan😁 Pure kotlin reactive extensions implementation would > be more lightweight and could definitely...

Not quite sure why that's really different or inherently more lightweight than a scheduler. On the JVM coroutines are backed by threads which loop on a queue just like schedulers....

That prevents SAM conversion. They should be replaced with lambda types. On Wed, May 10, 2017 at 10:23 PM Stepan Goncharov wrote: > My first goal with https://github.com/stepango/RxKotlin3-preview is >...

It is the case. The best way to solve this would be overloads though. On Wed, Mar 7, 2018 at 3:16 PM Thomas Nield wrote: > I think I reversed...