is there a standard of when to use higher order functions vs kotlinlang #announcements

Channels

100daysofcode

100daysofkotlin

100daysofkotlin-2021

androidgithubprojects

cincinnati-user-group

competitive-programming

event21-community-content

java-to-kotlin-refactoring

jvm-ir-backend-feedback

kotlin-multiplatform-contest

kotlinultimatechallenge

myndocs-oauth2-server

naming

navigation-architecture-component

practical-functional-programming

proguard

prozis-android-backup

refactoring-to-kotlin

russian-kotlinasfirst

skia-wasm-interop-temp

stayhungrystayfoolish

swagger-gradle-codegen

tricity-kotlin-user-group

Title

Andrew Gazelka

01/29/2019, 12:04 AM

is there a standard of when to use higher order functions vs interfaces with one method?

maybe it is just me, but

val permissions = HashSet<(CommandSender) -> Boolean>()

seems slightly jank

also HOF don't really specify what the function is doing whereas interfaces do

is having two functions, one accepting an interface and one accepting a HOF redundant? (HOF would be wrapped in interface)

Shawn

01/29/2019, 12:05 AM

conversely, interfaces generally don’t tell you what the function takes and returns

if you find yourself writing this type out a lot, maybe a typealias is a good middle ground?

Andrew Gazelka

01/29/2019, 12:11 AM

yeah, probably

ghedeon

01/29/2019, 2:08 AM

honestly, seems like HOF is often preferable even in case of interfaces with multiple functions. It's more granular and flexible this way. A good example would be

TextWatcher

on Andorid that got splitted into separate lambdas in ktx library.

#announcements Join Slack