Jake Wharton
Jake Wharton
There is an issue to replace the bundle factory with a type safe one once inline classes are available in Kotlin 1.3. They are not equivalent use cases anyway so...
I'm a bit hesitant about adding clicks because of how easy it creates leaks. Although it's no different than using the `ClickableSpan` subclass I suppose. Your syntax doesn't make sense...
Neither of those behaviors are intuitive for a method named "update". I agree that this method should only alter the drawables which are supplied. This is also solves your case...
Yep. That's what `TextView` does except we'll use `ContextCompat.getDrawable`.
I don't think we want to use `count` because it requires that the query backing the cursor traverse its entire result set. So if you query for a million items...
Why based on byte count and not size?
Why don't we lobby to have the framework method changed to use an unsafe type parameter cast like we did with `findViewById`?
With that you're going to cause confusion with two classes named `Log` unfortunately. I'm not sure logging extensions are all that useful in general since log calls tend to be...
We need to figure out a general multi-callback listener strategy... I'm going to coalesce these into a mega issue.