Jake Wharton
Jake Wharton
That isn't a problem with this proposal. All Kotlin behaves like that.
> For a sealed interface this proposal is not to attempt any protection scheme, but just compile an interface as if it was not sealed. We will introduce an IDE...
Reflection is a big hammer that almost guarantees violation of invariants. I'm not sure it's the best comparison. Polymorphism (i.e., implementing an interface) is an exceedingly normal thing. I think...
That PR was replaced with https://github.com/ReactiveX/RxJava/pull/4423 for `to()`
That is not the same problem. You need to enable Java 8 support: https://developer.android.com/studio/write/java8-support#supported_features
I don't think there's an urgency here, but we can consider supporting it long-term once it's stable and once Dagger has migrated.
Is this meaningfully different than holding a `StateFlow`? I remember us talking about it and we couldn't come up with reasons that you would explicitly need a `State` over `StateFlow`.
Yeah I'm not really opposed to adding this API. Like I said, we talked about exposing a `State`-producing factory very early on. I just want to understand its relationship to...
Matt and I talked about this a long time ago. I think the summary is that if you can hand a State directly to Compose UI then why not just...
(Someone reminded me of this at the talk. Thanks, person!)