Jake Wharton
Jake Wharton
> I don't see how it can cause any harm now or in the future. Using the refactoring option to introduce a typealias for a type which participates in the...
Most of the infrastructure for parsing this is already in `mosaic-terminal`, it just lacks a higher-level API for consuming it.
Retrofit is a Java library and uses Java reflection to pass type information to the body converters. As such, we don't get nullability information (at least until future versions of...
I'll bring this up with the kotlinx.serialization devs
Right so this is simply a limitation of using Java-based reflection and our inability to read the Kotlin module metadata to parse out the nullability of the inner type. There's...
Yeah I suspect this is due to the snapshot system and both us and Compose UI launching a coroutine to apply snapshots periodically, but would have to confirm that. It...
I do not have time to look at this any time soon. If no one else does, I'll get to it eventually.
> It also means that we likely can reproduce this in pure Compose (i.e., no Molecule) and potentially file a bug upstream. https://issuetracker.google.com/issues/329011032
Are you sure it's on the body parameter? The exception indicates you've trimmed down the example.
It might be better to replace it with a compare and swap loop with an atomic? We're not guarding an operation, just performing creation where only a single instance can...