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
n

Norbi

03/07/2023, 11:54 AM
I'm actively experimenting with
raise()
and I thought that I would like
x.ensureNotNull { ... }
better than
ensureNotNull(x) {}
. But then I've run into some compilation errors, see the code in my next message. 1. Maybe do you know if the internal compiler error in the first example is already reported? (I use Kotlin 1.8.0 and Arrow 1.1.6-alpha.36 but I have also tried with Kotlin 1.8.10 and 1.8.20-Beta) 2. How can I specify the "context" in the second example? Thanks.
import arrow.core.raise.Raise
import arrow.core.raise.RaiseDSL
import arrow.core.raise.ensureNotNull
import kotlin.contracts.ExperimentalContracts
import kotlin.contracts.InvocationKind
import kotlin.contracts.contract

context(Raise<R>)
@OptIn(ExperimentalContracts::class)
@RaiseDSL
public inline fun <R, B : Any> B?.ensureNotNull(raise: () -> R): B {
    contract {
        callsInPlace(raise, InvocationKind.AT_MOST_ONCE)
        returns() implies (this@ensureNotNull != null)
    }
    return this ?: raise(raise())
}

object E1
object E2

context(Raise<E1>, Raise<E2>)
fun f() {
    // Using arrow's ensureNotNull()
    ensureNotNull(1) { E1 } // 1: Internal error occurred while analyzing this expression: "IllegalStateException: Arguments and parameters size mismatch: arguments.size = 2, parameters.size = 3"

    // Using my ensureNotNull()
    1.ensureNotNull { E1 } // 2: How to workaround the compilation error "Multiple arguments applicable for context receiver"?
}
a

Alejandro Serrano Mena

03/07/2023, 12:25 PM
unfortunately due to erasure the compiler sometimes has problems figuring out
in theory you can use something like
context(r1@Raise<E1>, r2@Raise<E2>)
and then use the labels when calling the different things
n

Norbi

03/07/2023, 12:32 PM
Thanks, it really works for both examples but the syntax becomes uglier and less readable 😞
context(r1@Raise<E1>, r2@Raise<E2>)
fun f() {
    // Using arrow's ensureNotNull()
    with(this@r1) {
        ensureNotNull(1) { E1 }
    }

    // Using my ensureNotNull()
    with(this@r2) {
        1.ensureNotNull { E2 }
    }
}
s

simon.vergauwen

03/07/2023, 12:38 PM
You should be able to call:
context(r1@Raise<E1>, r2@Raise<E2>)
fun f() {
    // Using arrow's ensureNotNull()
    r1.ensureNotNull(1) { E1 }
}
c

CLOVIS

03/07/2023, 12:59 PM
I haven't seen that
r1@
syntax in the KEEP, where is it documented?
n

Norbi

03/07/2023, 1:14 PM
@simon.vergauwen it does not compile unfortunately:
context(r1@Raise<E1>, r2@Raise<E2>)
fun f() {
    with(this@r1) {
        ensureNotNull(1) { E1 }
    }

    r1.ensureNotNull(1) { E1 } // Compile error: "Unresolved reference: r1
}
s

simon.vergauwen

03/07/2023, 1:16 PM
this@r1.ensureNotNull(1) { E1 }
? @CLOVIS I remember seeing a discussion somewhere 🤔 but I cannot seem to find it anymore. It was about specific things like this so I guess it's not fully implemented yet.
c

CLOVIS

03/07/2023, 1:18 PM
There was a big discussion on the KEEP on whether to allow
context(name: Type)
, from what I remember Roman Elizarov explained that adding labels was not in line with their goals. I'm surprised they added syntax to do it, in the end.
n

Norbi

03/07/2023, 1:20 PM
this@r1.ensureNotNull(1) { E1 }
This works :)
s

simon.vergauwen

03/07/2023, 1:21 PM
There needs to be some way to distinct between different elements, right? 🤔 So some form of labels is required, I'd say that
label@
is much more in line with what we already have in the language comaared to
name: Type
n

Norbi

03/07/2023, 1:23 PM
I would have preferred the
name: Type
decision because then we would not need to always write the
this@
prefix - but that's just my opinion :)
c

CLOVIS

03/07/2023, 1:26 PM
Well the KEEP originally forbid having the same type multiple times as receiver, so there was no need to disambiguate, and the type could be used as label (e.g.
this@Raise
). I liked the parameter name because they are a kind of parameter, but Roman brought very good arguments against that. I'm sure that discussion was part of the decision for that label syntax. @Norbi I think your probably happens because it's not stable yet, and when it is you won't need to explicitly label receivers in your examples
n

Norbi

03/07/2023, 2:06 PM
I think your probably happens because it's not stable yet, and when it is you won't need to explicitly label receivers in your examples
Let's hope so 🙂 I've reported it just to be sure: https://youtrack.jetbrains.com/issue/KT-57176/Internal-compiler-error-when-using-multiple-context-receivers
@CLOVIS, it seems that the explicit label will be required with K2 as well:
With K2:
With implicit context receiver, call is ambiguous. Specify the receiver explicitly
c

CLOVIS

03/07/2023, 2:40 PM
I understand that to mean "with the current build of K2" and not "with the final version of K2", but I could be wrong.