I mean, strictly speaking it’d probably be somethi...

# announcements

[Shawn]

I mean, strictly speaking it’d probably be something like

inline fun <reified T> Any.castTo() = this as T

but a) that probably won’t work, b) why do you need this as a function?

[tyjka]

Plain curiosity. And maybe

holder.castTo(NetworkStateViewHolder).bindTo(networkState)

looks more fluid to me than

(holder as NetworkStateViewHolder).bindTo(networkState)

Later is more idiomatic though.

[tyjka]

And yes, it doesn’t work

[Shawn]

fixed the syntax

[Shawn]

in your case, usage would be

holder.castTo<NetworkStateViewHolder>()
    .bindTo(networkState)

[Shawn]

still don’t recommend it, but it works in my scratch file

[tyjka]

Thanks, it works! Can you please elaborate on why you think it’s a bad idea? Apart from being not idiomatic?

[Shawn]

mostly just that it’s not idiomatic, and that also if you’re ever in a situation where you’re okay with returning null if the class cast fails, you’ll just have to switch from the function to (foo as? bar)?.baz()... anyhow or add an additional castToOrNull<>() function

[Shawn]

It’s just, kinda clumsy to replicate an existing language feature, but I suppose there’s nothing inherently bad about it

[tyjka]

Thanks for your help. Anyways, it helped me to learn something new about language features))