Jake Wharton

From content-based array `toString()` in Java bytecode: ``` 221: aload_0 222: getfield #15 // Field generic:Ljava/lang/Object; 225: checkcast #66 // class "[J" 228: invokestatic #156 // Method java/util/Arrays.toString:([J)Ljava/lang/String; 231: dup...

The (even further) upstream issue is https://youtrack.jetbrains.com/issue/KT-64109. Once this is fixed, we can `compileOnly` every target automatically. It doesn't seem _too_ far away, so I'd be hesitant to make a...

Ah, interesting. I didn't read the full comment history since they decided to dupe my (older 😬) bug onto it: https://youtrack.jetbrains.com/issue/KT-43500. I only was notified of the most recent comment...

We can add it to the associated compile-only configuration for tests, too!

I believe I tried that and KGP won't let you. You can't make the common metadata target have different behavior across platform targets.

Those are the replacement character which occurs when there's malformed encoding (presumably of UTF-8). I don't think we take into account printable vs. non-printable characters which is why it screws...

> Is there any special reason for storing multiple BehaviorDelegates though? Pre-dates open sourcing when it was being used for multiple views at once. The assumption can be removed.

No. That question is not a bug but a feature. On Sat, Jun 4, 2016, 3:38 PM Rúben Sousa [email protected] wrote: > Is it the same issue with the existing...

If it's a bug it should be reported to b.android.com then. But it's not the same issue, this occurs after the up event. On Sat, Jun 4, 2016, 3:46 PM...

Right now it's more of an experiment. On Sat, Jun 4, 2016, 4:07 PM Rúben Sousa [email protected] wrote: > Ok, I'll try to reproduce it. Thank you for making this...