Is there a way to have early-return behavior in composables from sub-functions without using exceptions? In standard Kotlin, we can use exceptions for early return:

// this is not idiomatic, just an extremely simplified example
fun foo(bar: String): Int {
    val int = bar.toIntOrNull()
    requireNotNull(int) { "Early return here" }
    return int
}

Using Arrow, the

either

comprehension enables similar features:

fun foo(bar: String): Either<String, Int> {
    val int = bar.toIntOrNull()
    ensureNotNull(int) { "Early return here" }
    return int
}

Using Flows, similar behavior can be emulated using

catch

:

fun foo(bar: Stirng): Flow<Result> = flow {
    val int = bar.toIntOrNull()
    requireNotNull(int) { "Early return here" }
    emit(Result.success(int))
}.catch {
    if (it !is IllegalArgumentException) throw it

    emit(Result.failure(it))
}

Which brings it to my question: what is the equivalent with

@Composable

functions?

Hello, is there any way to disable swipe gestures for HorizontalPager. i want to manage the swipe manually via the pager state.

Is it possible to get IntelliJ to list unused imports in the whole project? I've got

Settings -> Inspections -> Kotlin -> Unused import directive

set to "Warning", but when I build the project I don't see any unused imports listed. I can only see them by going to individual files in the editor and looking for greyed-out import statements. When looking at Java projects, on the other hand, I can see a list of used imports when I build.

Is there a way to dynamically modify tables? Instead of adding a new column in the table definition, can I do something like

transaction{
   Table.addColumn(...)
}

?

How to resolve this issue Unresolved reference: Res

Res.drawable.ic_facebook

Unresolved reference: <projectName>.composeapp.generated.resources.*

In my compose desktop application, I want the user to start voice input with the space key. However I obviously don't want that to happen if the user is in a textfield, as they may be using the space key as part of their text input. I expected text fields to consume the key event, however I still get the event on the window even when a textfield is selected (it also adds the space in the texfield). Any idea how to avoid it?

Window(
    ...
	onKeyEvent = { keyEvent ->
		if (keyEvent.key == Key.Spacebar && keyEvent.type == KeyEventType.KeyDown) {
			println("Got space") // happens even when a textfield consumes the key event first
			true
		} else {
			false
		}
	}
)

I know AutoSizing/Shrinking Text is on the Compose roadmap, but it's not clear when that will actually happen. I've seen some gists that iteratively make use of Text's

onTextLayout

closure. But I was asking myself, why not just use a Canvas rather than a Text if I'm just after simplified single line Text drawing, and want to specify a "minimum font size". Curious why this would be a bad idea? Or if I'm missing obvious things? Code on thread

hello everyone. how are you handling one-time events between the viewmodel and compose? snackbars and navigation for example

Can this With | old Native GC, variable in singleton without @ThreadLocal can't be changed after initialization | warning be ignored in Kotlin 1.8.10?

I’m getting a report in crashlytics with this stacktrace. Crashlytics points

kotlin::FormatToSpan(kotlin::std_support::span<char, 18446744073709551615ul>, char const*, ...) + 4354272500

to be the culprit. I have no Idea how to find what causes this, how should I proceed?