ianbrandt
10/15/2024, 4:56 PMianbrandt
10/15/2024, 5:02 PMianbrandt
10/15/2024, 5:19 PMianbrandt
10/15/2024, 5:24 PMianbrandt
10/18/2024, 8:19 PMJP Sugarbroad
12/03/2024, 10:09 PMConsumer<? super ThingBuilder>
and when I try to use them from Kotlin the ThingBuilder
is an argument instead of a receiver. Is there any annotation I can use to mark that this should be a receiver, or am I stuck wrapping everything?JP Sugarbroad
02/24/2025, 12:31 AMimplements KeySelector
with no type arguments at all. I can't find a bug tracking this, does anyone know of one before I open a new one?zt
06/21/2025, 6:28 AMIan Botsford
07/02/2025, 9:25 PMenable
vs no-compatibility
vs disable
. The documentation gives little blurbs but the implications are not clear:
•Maintain compatibility how? My K-2.2 lib can call a K-2.1 lib? A K-2.1 lib can call my K-2.2 lib? Something else? Can I imply that neither of the other options maintain binary compat with older Kotlin versions? (seems like(default): generates default implementations in interfaces and includes bridge functions in subclasses andenable
classes. Use this mode to maintain binary compatibility with older Kotlin versions.DefaultImpls
disable
might)
• `no-compatibility`: generates only default implementations in interfaces. This mode skips compatibility bridges andWhat're the implications of skipping compatibility bridges andclasses, making it suitable for new code.DefaultImpls
DefaultImpls
classes? Why are those good/bad things?
• `disable`: disables default implementations in interfaces. Only bridge functions andWhat're the implications of disabling default implementations in interfaces? Why are those good/bad things?classes are generated, matching the behavior before Kotlin 2.2.0.DefaultImpls