https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
c

CLOVIS

05/14/2023, 12:12 PM
I tend to write a lot of code like the following (sorry for the lack of imagination in naming):
sealed class ParsingError {
    object InvalidFormat : ParsingError()
    object InvalidArguments : ParsingError()
}

fun parse(…): Either<ParsingError, SomeType> = TODO()

sealed class ComputationError {
    data class ParsingError(val error: ParsingError) : ComputationError()
    object SomeOtherError : ComputationError()
}

fun computation(…): Either<ComputationError, SomeType> = either {
    val a = parse(…)
        .mapLeft(ComputationError::ParsingError)
        .bind()

    …
}
The
.mapLeft().bind()
is quite verbose and appears a lot… is there some nice API I'm missing to simplify it? It seems it would be even worse with context receivers, because I would be forced to add an
either {}
block to all sub-function calls, defeating the purpose
y

Youssef Shoaib [MOD]

05/14/2023, 1:18 PM
Why not do this with context receivers:
context(Raise<ParsingError>)
fun parse(…): SomeType = TODO()
context(Raise<ComputationError>)
fun computation(…): SomeType {
    val a = recover({parse(…)}) { 
        raise(ComputationError.ParsingError(it) 
    }
    …
}
It allows you to call
parse
while handling its error by raising another error. You could also do a similar thing with
effect
or
either
, but why over complicate things?
recover
is made to do exactly this, and it allows you to sometimes treat the error as success if you really want to
c

CLOVIS

05/14/2023, 1:19 PM
I'm on Kotlin/JS, I don't have context receivers…
y

Youssef Shoaib [MOD]

05/14/2023, 1:19 PM
Oops, well, the inner part with parse and raise still works, you'll just have to do
parse().bind()
c

CLOVIS

05/14/2023, 1:20 PM
So something like this?
recover({ parse(…).bind() }) {
    raise(ComputationError.ParsingError(it))
}.bind()
y

Youssef Shoaib [MOD]

05/14/2023, 1:20 PM
No need for that last bind.
parse
in your case will return an Either, hence why we need to bind it inside
recover
, but afterwards
recover
will just return the value itself
c

CLOVIS

05/14/2023, 1:21 PM
Seems less readable to me 😕
The real code
I guess if there was a
recover
overload that always raised it would be nicer:
recover({ field.validate().bind() }, Form.Failures::InvalidImport)
IMO that looks close to optimal for this case
y

Youssef Shoaib [MOD]

05/14/2023, 1:29 PM
With context receivers though I think it makes more sense. Also, you can define something like this:
public inline fun <OuterError, Error, A> Raise<OuterError>.withMappedErrors(
  @BuilderInference errorMapper: (error: Error) -> OuterError,
  @BuilderInference block: Raise<Error>.() -> A,
): A = fold(block, { throw it }, { raise(errorMapper(it)) }, ::identity)
Which makes the code like this:
fun computation(…): Either<ComputationError, SomeType> = either {
    withMappedErrors(ComputationError::ParsingError) {
        val a = parse(…).bind()

    …
    }
}
And the bind goes away if you use context receivers. One thing I'm not sure of is if the
@RaiseDsl
DslContext
annotation might prevent you from raising
ComputationError
inside of the
withMappedErrors
. If Intellij does complain, you can either suppress the warning, or (with context receivers) make withMappedErrors re-apply the outer Raise context like this:
public inline fun <OuterError, Error, A> Raise<OuterError>.withMappedErrors(
  @BuilderInference errorMapper: (error: Error) -> OuterError,
  @BuilderInference block: context(Raise<Error>, Raise<OuterError>) () -> A,
): A = fold(block, { throw it }, { raise(errorMapper(it)) }, ::identity)
c

CLOVIS

05/14/2023, 1:31 PM
Actually, that
withMappedErrors
function looks great. Should I create a feature request for it?
y

Youssef Shoaib [MOD]

05/14/2023, 1:34 PM
Absolutely! I think it might be a useful pattern. It probably needs a better name though. It might also not work because of
ResultDsl
, so it might have to wait until context receivers are stable
c

CLOVIS

05/14/2023, 1:53 PM