The class?

The function’s type param is reified as you wrote it.

one sec

the following works, depends on kotlin-reflectl (need to add to your gradle/maven org.jetbrains.kotlinkotlin reflect1.3.0)

you can do a bit more checking maybe filter on creation function instead of .first() and there might some kotlin wrapper instead of dropping to ::class.java too but an exercise for another time. maybe enforce the create on the interface Createable too rather than just a marker interface.

also I guess that can be : T rather than T?

val dave = "dave".buildSomething<Person>()

And the maths to "just work" (tm)

No you're probably right, normal Byte and Short don't have shifts either.

I might be able to fake it with

ByteArray

From Moshi’s readme:

Moshi is a great JSON library for Kotlin. It understands Kotlin’s non-nullable types and default parameter values. When you use Kotlin with Moshi you may use reflection, codegen, or both.

But that part about non-nullable types and default parameters is true only when using codegen, right?

I’ve used reflective moshi thinking non-nullable and defaults just work. Possibly. I’m vaguely certain I ran into no such problems. Could be that the json in question had no such requirements and I just dodged that particular bullet through luck alone. How come the defaults and non-nullable shouldn’t work on reflection? Im not very knowledgeable about kotlin reflection.

@Mika Puhakka See https://github.com/square/moshi#default-values--constructors and https://www.bignerdranch.com/blog/when-nullability-lies-a-cautionary-tale/

Hmm that is certainly new information for me, maybe someone more experienced with moshi can confirm your question.

@Mika Puhakka I think you are right, there should be no problems if you use it as documented (have

.add(KotlinJsonAdapterFactory())

when building Moshi), I missed that part and didn’t have

moshi-kotlin

in my project when testing it.

Hmm yeah that’s pretty much what I have. Along with

Rfc3339DateJsonAdapter().nullSafe()

for dates and some custom adapters.

yes

agreed 😄

Is there any DI frameworks that built on top of Kotlin compiler plugin API?

Is it ok to reuse the serializer object in the kotlinx serialization library?

Packet.serializer() is it returning the same instance all the time?

Is there a function with an Any? receiver that basically converts the object to something else based on a functional param?

like map but for single objects

sweeet

thank you

is there a similar function that returns Unit?

There are

also

,

apply

,

let

and

run

. None return

Unit

though.

oh, run is what i was looking for I guess

But that’s not really any different than let, is it?