Any ideas on a good approach to map C bitfields often used as flags in C functions to a nice typesaf...

# kotlin-native

[vbsteven]

Any ideas on a good approach to map C bitfields often used as flags in C functions to a nice typesafe (or at least descriptive/discoverable) Kotlin API ?

I'm trying to become an API like

val application = Application("myapp", ApplicationFlags.NONE.or(ApplicationFlags.REPLACE))

where I want the signature to read something like

class Application(val name: String, flags: ApplicationFlags)

So the user does not have to go hunt for random constants.

[kevin.cianfarini]

I talked about this previously herre. https://kotlinlang.slack.com/archives/C0B8Q383C/p1672886309003409

[vbsteven]

Thanks, that OptionSet you proposed in the thread looks interesting.

[kevin.cianfarini]

If you want to do this in an allocation free way I suggest not using the OptionSet interface and instead just exposing utility functions atop a value class.

[vbsteven]

I'm still looking into it and experimenting, for the thing I'm working on they are mostly used for infrequent UI-thread method calls, so having the allocation does not hurt performance that much I guess.

[vbsteven]

I'm not very familiar with value classes in Kotlin, so that's another thing I'll have to look into

[kevin.cianfarini]

The tl;dr on value classes is that if you don’t use them in a way that requires polymorphism (eg referring to it as an interface type), then whatever the value class wraps is what’s passed around in bytecode.

There’s no allocations, no pointer chasing, etc.

[kevin.cianfarini]

If you’re familiar with Compose, Dp is a value class.

[kevin.cianfarini]

@Immutable
@kotlin.jvm.JvmInline
value class Dp(val value: Float) : Comparable<Dp> {

[kevin.cianfarini]

At runtime only a float will get passed around, not an instance of Dp (unless it’s referred to as a Comparable<Dp>)

[vbsteven]

I've seen it but not used it that much, my general dislike for Compose/SwiftUI/React is the reason I'm looking in KN/GTK...

[vbsteven]

but that's very useful information on the value classes. thanks

[kevin.cianfarini]

No problem